The 000000-dev branch in this repo (i.e., the default branch) has just been renamed to dev (simpler, easier to type). IMPORTANT: This change may impact anyone who has a fork of this repo on GitHub. If you have any trouble in the future; i.e., errors about a missing branch or problems when trying to sync with the upstream repo, please follow these instructions to bring your fork up-to-date.
Updating Your Fork (Instructions)
Update Your Local Clone
$ cd [YOUR LOCAL REPO DIRECTORY]
$ git checkout 000000-dev
$ git branch --move dev
Push dev To GitHub Now
$ git push --set-upstream origin dev
Delete Old 000000-dev Branch
Go to GitHub and change the 'default' branch in your fork to dev
Then run the following command to delete the old 000000-dev branch from GitHub.
$ git push origin --delete 000000-dev
Or, you can simply visit the 'Branches' tab in your fork at GitHub and delete it that way.
What's Next?
If you already followed these instructions provided by GitHub in the past, you're all set. Nothing in this change should negatively impact an already-configured upstream remote. If you haven't followed those instructions (i.e., you don't yet have an upstream remote configured), you might want to take a moment to do that now.
Attn: Contributors w/ a Fork
The
000000-devbranch in this repo (i.e., the default branch) has just been renamed todev(simpler, easier to type). IMPORTANT: This change may impact anyone who has a fork of this repo on GitHub. If you have any trouble in the future; i.e., errors about a missing branch or problems when trying to sync with the upstream repo, please follow these instructions to bring your fork up-to-date.Updating Your Fork (Instructions)
Update Your Local Clone
Push
devTo GitHub NowDelete Old
000000-devBranchGo to GitHub and change the 'default' branch in your fork to
devVisit:
https://github.com/[YOU]/[REPO]/settings/branchesThen run the following command to delete the old
000000-devbranch from GitHub.Or, you can simply visit the 'Branches' tab in your fork at GitHub and delete it that way.
What's Next?
If you already followed these instructions provided by GitHub in the past, you're all set. Nothing in this change should negatively impact an already-configured upstream remote. If you haven't followed those instructions (i.e., you don't yet have an upstream remote configured), you might want to take a moment to do that now.