Create section: branch renaming#1476
Create section: branch renaming#1476ben merged 13 commits intoprogit:masterfrom HonkingGoose:feature/add-section-change-existing-branch-name
Conversation
ben
left a comment
There was a problem hiding this comment.
I like the direction you've got here, and it doesn't feel like it's very far from being done.
|
Hi @ben,
Man writing technical docs is hard... especially for something as complicated as changing the master branch. Should we include links to GitHub documentation, for things like: Should we mention things like Dependabot/Travis CI by name, to help users understand what kind of things might break? Maybe we should instruct readers to merge or close all pending pull requests that are targeting master before making the move. As this will save a lot of headaches when trying to merge the pull-request via the GitHub/Gitlab interface. (I tried re-targeting pulls that targeted the old Do we want a vendor neutral text, or do we want to mention GitHub specific gotchas? HonkingGoose |
- Remove unnecessary comma - Explain what happens what the result is after changing your branch name and pushing the changed branch to the remote Co-authored-by: Ben Straub <ben@straub.cc>
- Warn about changing the mainline branch.
- Add item to list - Explain how to remove the master branch
ben
left a comment
There was a problem hiding this comment.
Super close, just a couple more suggestions.
Co-authored-by: Ben Straub <ben@straub.cc>
Co-authored-by: Ben Straub <ben@straub.cc>
|
Ready for review and possibly a merge. |
Add a new section dealing with renaming branches containing:
masterbranch willy-nilly.This is a rough draft, and will need some feedback to get it ready for merging.
I also think some other files will need to be changed as well, so that it's all properly referencing each other. I'm really not sure where those references should be. So I could use some help with that. 😄
This PR will help with issue: #1462