You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test coverage expectations: minimum 80 for all files in Stmts, Branch, Funcs, and Lines
PR size expectations: reviewable within 1-2 hours
Branch amount limits: Max 2 working feature branches, max 3 in-review branches
Dependency updates: security bumps > Major bumps > minor bumps > patch bumps
branch naming conventions: "feature/branch-name" or "bugfix/branch-name"
PR naming conventions: see branch naming
commit message conventions: should be concise, meaningful, and convey the purpose of the changes. A recommended convention is to use imperative language and start the message with a verb. For example, "Add user authentication feature" or "Fix bug in payment processing module." Additionally, including a reference to the associated issue or user story number in the commit message can provide better traceability.
Code formatting: JS=prettier, python=black
The text was updated successfully, but these errors were encountered:
h701h
changed the title
Create list of Trunk based development guidelines for Tracker
Create list of DevSecOps improvement/development guidelines for Tracker
Mar 25, 2024
The text was updated successfully, but these errors were encountered: