On the Standardization of the use of git

the unfinished code on the day of submission (the function has not been written yet). How do you usually write commit for submission? Still don"t submit it if you haven"t finished it

.

is there a general team specification?

Feb.28,2021

in this case, do not submit as much as possible, and try your best to ensure that each submission can successfully pass the build test.

if you're just recording locally, commit, or even stash is fine (as long as you remember, stash is easily forgotten)

you can rewrite commit directly using commit-- amend before formal submission.

if you expect to continue development at home, you may do push. Then ask push to go to his own warehouse, after the home change, the same commit-amend after push-f forcibly overwrites the commit of his own warehouse.

try not to have spam in commit records


it's okay to submit directly, as long as you don't git push . Submission only affects you locally.

generally, if I don't finish the code, I put it in the storeroom (I often use it when doing multi-function branch transfer), git stash . In this way, it can not affect the future work, but also can keep the current branch clean, but also can go to other branches.

it is recommended that git commit or other actions be done at the end of the day, because it is important to keep a git work track for the day.


must be written, which is very important. You can refer to these two specifications. Here is how to add git commit

.
Menu