The following is a guideline on how to commit your code.
Assuming Git as the Version Control System. However, the following concepts can be used for any Version Control System.
- I want to use the same git workflow as much as possible, on different projects.
- My pull requests should be easy to review and debug.
- Have an easy way to setup my workflow and configure.
- Ensure linting and security.
- Should be able to make changes to my workflow easily.
git diff --check, which identifies any possible whitespace errors and lists them for you. This can be added as a git hook potentially.
Commit messages should be around 50 to 60 characters long, at max, similar to how one limits 120 characters perline when writing code.
Make seperate commits for logically seperate changes.
- Use imperative tone , for your commit messages.
- Example :
Make IndexController check for tokenover
Made changes to ensure IndexController checks for token
- Reason: More concise and the intent of the change is understood right away.
- Example :
- Using git config i.e.
.gitconfigfile , to set the up required info. Such as :
- GPG signature, Author info
- Reason : To make the commit more readbale and secure. This totally depends on the usecase.
- Check if any sensitive info is checked in as part of the commit. One should have an automated way, of checking this type of change.
- Reason : So that the security exposure is minimised and when automated, the cost of setup is minimal going forward.
- It’s also scalable, when working in a team and easier to enforce rules.
- Tools to enforce the checks:
- More at info at : https://geekflare.com/github-credentials-scanner/
- Automate as much as of the git workflow, as possible. Ensure the onboarding of this workflow is simple or atleast not too cumbersome. You can make incremental changes over time.
Sources I have used for reference:
For any feedback, you can tweet me at : @vaikuntj .