- everything begins with an issue
- always check the current branch before making any changes
- run "git pull" as often as possible
- commit as soon as possible
- commit should be referenced to the related issues
- never push changes to the main branch directly
- always keep the tree tidy by cleaning old branches
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (4)
I can suggest
and
yes, commit message should be concise, clear and meaningful. There are some rules to write good commit messages, depending on the git flow you choose. What I mentioned here are general.
Great habits!
This is the code I use for keeping local branches tidy. Sharing in case it helps anyone else.
What about commits message on how it should be written? and how do your format your code before you changed it? and how about branch naming? and how about git rebase to fetch last changes in the main branches :')))))))