The name of the branch when executing the retrieval request

I have already made several requests to download GH, but I devoted myself to the master branch. Now I read in different places that it’s nice to create a branch.

Are there any guidelines for naming branches? I usually work with Mercurial and give my branches the same name as the corresponding error identifier identifier, but this does not work for this.

I looked at several repositories: some are fixed on master , some are fixed on fix-somebug , some are fixed on patch-1 . I understand that this does not create conflicts because download requests are merged into master (or another long live branch) and the branch is then deleted, is this true?

+4
source share
2 answers

The idea behind the pull request branch is to allow the automatic removal of the specified branch after accepting the transfer request.

And from April 2013, this thread will be deleted for you :

merge button

Then you need to update / reinstall your master from the upstream repo master to get what you developed to isolate the branch from the official repo that you have forked (since this repo accepted your pull request)

upstream

The branch name should be the development process in which you are participating.

+8
source

It is always recommended that you commit on git branches, not on master. You can use any name for the git branch (it does not allow spaces in branch names, as well as some special characters).

0
source

Source: https://habr.com/ru/post/1489453/


All Articles