[Github's Repository Custom] Does the role/description of each branch generally not work?

Asked 2 years ago, Updated 2 years ago, 41 views

I'm a beginner at Github.
Does the role/description of each branch generally not done on README.md?
(I think it's related to Github's repository custom.)

Looking at various repositories
There are many branches that I don't know exactly what kind of branch it is.
I understand that most of them are for renovation, but
I'm sure there are people who don't understand that. When I wanted to clone it, I switched to a working branch without realizing it.
We can assume that you have cloned it.
With that in mind, I think it would be kind of you to explain the branch somewhere.
Do you generally not explain branches?

It's been a long time, but I appreciate your cooperation.

Prerequisite Awareness
·Branch is a work place, and version control is usually done with tags.
·Remote branch includes main branch with the latest version and develop branch in progress.
"·The contents of each version's update are in the ""releases"" description field, the release topic on README.md, and
"  Commonly described on RELEASE.md.
·If visitors want to download the data,
 Many download clones and zips from the "releases", "tags", and main branches.

github

2022-09-29 22:00

1 Answers

In cases where multiple users push directly to a common remote repository, it certainly seems necessary to match the operational rules of the branch, but GitHub can basically only write to the owner himself and to authorized users.

If you want to work in a local repository or forked repository, you can use a free branch name, so you don't need to explain it to a third party.

On the other hand, when you receive a pull request, you often see instructions such as "Please send a pull request to a designated branch such as develop instead of the main branch."


2022-09-29 22:00

If you have any answers or tips


© 2024 OneMinuteCode. All rights reserved.