| Commit message (Collapse) | Author | Files | Lines | ||
|---|---|---|---|---|---|
| 2022-10-27 | feat(ops/github): archive notes.fcuny.net | Franck Cuny | 1 | -3/+1 | |
| The content has been merged with fcuny.net - I can keep everything in one site. | |||||
| 2022-10-25 | ref(ops/github): finished the migration of my repositories | Franck Cuny | 1 | -54/+59 | |
| All the repositories should be on GitHub now, and archived if they are not relevant anymore. | |||||
| 2022-10-24 | feat(ops/github): import more repositories | Franck Cuny | 1 | -0/+184 | |
| 2022-10-24 | fix(ops/github): create resources in correct order | Franck Cuny | 1 | -0/+2 | |
| We first need to create a repository before we can create the default branch. For the default branch to be set, we also need the repository to contain a commit, which is achieved with the `auto_init' attribute. We can always push with `--force' to overwrite that initial commit when doing the migration. | |||||
| 2022-10-24 | ref(tools/mpd-stats): delete the project | Franck Cuny | 1 | -0/+3 | |
| It's been moved to its own repository at https://github.com/fcuny/mpd-stats Update the list of repositories managed by terraform. | |||||
| 2022-10-23 | ref(ops/github): only allow merge commit | Franck Cuny | 1 | -3/+3 | |
| While not great, this is the default workflow on GitHub. It's also what allows my `git-broom` CLI to work with branches on GitHub. | |||||
| 2022-10-22 | feat(ops/github): new repository: x509-info | Franck Cuny | 1 | -0/+4 | |
| 2022-10-22 | fix(ops/github): some fixes related to repositories creation | Franck Cuny | 1 | -3/+3 | |
| 2022-10-15 | ops(github): archive the repository govanity | Franck Cuny | 1 | -3/+1 | |
| 2022-10-09 | feat(ops/github): set the name of the default branch | Franck Cuny | 1 | -0/+13 | |
| From now on we should always be using 'main'. If a project requires 'master', it will need to be set explicitly. | |||||
| 2022-10-09 | ref(ops/github): simplify the configuration | Franck Cuny | 4 | -373/+125 | |
| Move all the repositories in a YAML file, instead of declaring each repository. This will simplify the management as I'll be introducing more resources to manage my repositories. | |||||
| 2022-10-08 | feat(ops/github): add the repository twitter-backup | Franck Cuny | 1 | -0/+14 | |
| 2022-10-08 | ref(tools/govanity): moved back to its own repository | Franck Cuny | 1 | -0/+14 | |
| It's back at https://github.com/fcuny/govanity | |||||
| 2022-10-04 | feat(ops/github): add notes.fcuny.net and containerd-to-vm | Franck Cuny | 2 | -0/+28 | |
| 2022-10-04 | feat(ops/github): add repository for fcuny.net | Franck Cuny | 1 | -0/+14 | |
| 2022-10-04 | ops(terraform): individual actions for init/plan/apply | Franck Cuny | 2 | -2/+31 | |
| Don't do all of these actions together, instead provide helpers for both init, plan, and apply. | |||||
| 2022-10-02 | feat(ops/github): new repository: gh-ssh-keys | Franck Cuny | 1 | -0/+14 | |
| 2022-09-30 | ops(github): terraform configuration to manage GitHub | Franck Cuny | 5 | -0/+354 | |
| Import current GitHub repositories into terraform. This should be the main way (going forward) to interact with GitHub to create / manage the repositories and ensuring I'm consistent in the ways I want to use it. | |||||
