Closed jsignell closed 3 years ago
Does the branch rename itself create a notification?
Does the branch rename itself create a notification?
No, but I am making these issues on every repo.
EDIT: Well actually in the github UI it makes a notification. Take a look at https://github.com/dask/dask-examples to see what that looks like
Right, but git fetch origin
should happen after the branch is actually renamed - I suppose when this issue is closed.
Yeah if you have suggestions on how to word these issues better, please let me know :)
What you need to do
to
What you need to do
Once the name on github is changed (the first box above is Xed, or this issue closed)
Maybe also note that push/pulling from the previous default branch will still work due to github redirects? This should cause a message in the terminal, but I haven't tried it. Whatever the message is, that's what people might search on in the future.
Thanks for handling this! One of those no-fun tasks...
better?
Yes, perfect. I thought about it a moment, and yes it makes sense that people would first see a problem on pull
, because presumably if you were to push to your fork/master, that would still be fine, and any PR would pick the default upstream branch without trouble - not that you normally PR from your default branch anyway.
@jrbourbeau and I are in the process of moving the default branch for this repo from master to main.
What you'll see
Once the name on github is changed (the first box above is Xed, or this issue closed), when you try to
git pull
you'll getWhat you need to do
First: head to your fork and rename the default branch there Then: