wpsharks / phings

Just a few Phings we like to use :-)
GNU General Public License v3.0
1 stars 0 forks source link

000000-dev => dev #124

Closed jaswrks closed 8 years ago

jaswrks commented 8 years ago

The dev branch will be referenced as just dev instead of 000000-dev.

Considerations


Attn: WebSharks Project Leads

Instructions for Updating websharks/ Repos

Rename Your Own Local Clone

$ git checkout 000000-dev
$ git branch --move dev

Push dev to GitHub :octocat:

$ git push --set-upstream origin dev

Change the Default Branch @ GitHub :octocat:

Visit: https://github.com/websharks/[REPO]/settings/branches

Delete Old 000000-dev Branch @ GitHub :octocat:

$ git push origin --delete 000000-dev

Or, you can simply visit the 'Branches' tab at GitHub and delete it that way.

Complete The Following Checklist (For Each of Your Repos)

jaswrks commented 8 years ago

Latest Phings: https://github.com/websharks/phings/releases/tag/160627.38807 Latest Hubflow: https://github.com/websharks/hubflow/releases/tag/160627 Latest HB Formulas: https://github.com/websharks/homebrew-formulas/releases/tag/160627

jaswrks commented 8 years ago

Attn: Contributors w/ a Fork

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

Visit: https://github.com/[YOU]/[REPO]/settings/branches

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.

raamdev commented 8 years ago

@jaswsinc FYI, I've checked off all the todos at the top of this issue. This issue can probably be closed now.

jaswrks commented 8 years ago

Cool!