Skip to content

Commit

Permalink
DOC: specify changing default branch to main
Browse files Browse the repository at this point in the history
  • Loading branch information
ColmTalbot committed Oct 3, 2024
1 parent 9fd23c4 commit 3b54531
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions MIGRATION.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@ If you have existing clones (and muscle memory), make sure you always use `main`
## Migrating development to GitHub:

- [create a fork of github.com/bilby-dev/bilby if you don't already have one](https://github.com/bilby-dev/bilby/fork)
- if you already have a fork on GitHub, you will likely need to [manually update the default branch to `main`](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch)
- fetch all upstream changes `git fetch --all && git pull`
- if git.ligo.org/lscsoft/bilby or a personal fork on git.ligo.org is in your remotes, remove it. Use `git remote -v` to see remotes and `git remote remove` to remove them (they can be added again if needed)
- add your fork on github as a remote `git remote add origin [email protected]:${ME}/bilby.git` (see, e.g., [here](https://stackoverflow.com/questions/9257533/what-is-the-difference-between-origin-and-upstream-on-github) for remote nomenclature)
Expand Down

0 comments on commit 3b54531

Please sign in to comment.