> I have above 200 feature branches in my local > repository. Will renaming
> the master branch cause any problems?
It should not be any problem at all. If you have some open PRs from some of
those branches, they will be automatically retargeted to the new branch
name in GitHub automatically.
On
Hi Serhiy,
On Thu, Mar 11, 2021 at 8:33 AM Serhiy Storchaka wrote:
> I have above 200 feature branches in my local repository. Will renaming
> the master branch cause any problems?
I don't think that you need to do anything on your machine nor on your open PRs.
When I use "git switch -c new_bra
10.03.21 16:06, Pablo Galindo Salgado пише:
> # What you need to do?
>
> You just need to update your local clone after the branch name changes.
> From the local clone of the repository on a computer,
> run the following commands to update the name of the default branch.
>
> $ git branch -m maste
Thanks for the response!
No. It has been discussed by the Steering Council as you can see in the
> February update:
> https://github.com/python/steering-council/blob/main/updates/2021-02-steering-council-update.md
>
>
Ok, great, I assume the missing bits will be coming in the March update
Steve
_
I am answering this as a member of the release management team, not as an
official response from the SC.
> and understand who the identified impacted parties are
All developers that have clones of the repository and any party maintaining
any script that interacts with the default CPython branch.
Hi
I would be great to read the impact analysis for this change, and
understand who the identified impacted parties are, and what the plan is to
notify them and help them update within this timescale.
Has this analysis been published anywhere? I know there are lots of places
where discussions/doc
