Rules Hub
Coding Rules Library
← Back to all rules
Rule priority, scope & exceptions
Use this to align rules with the senior-level structure (P0/P1/P2, scope, exceptions/tradeoffs).
communication ruleP1universalStack: General
communicationworkflowreportingrepository
State which repository the changes were made in
When reporting completed work or edits, always explicitly name the repository the changes landed in (and the branch when relevant), so it is never ambiguous which repo was touched.
PR: User directive 2026-07-10Created: Jul 10, 2026
Bad example
Old codets
| 1 | Done — fixed the avatar bug and added a test. All green. |
Explanation (EN)
Objašnjenje (HR)
Good example
New codets
| 1 | Done — fixed the avatar bug and added a test in the `hegnar-web` repo (branch `bugfix/FCK-3150-...`). All green. |
Explanation (EN)
Objašnjenje (HR)
Notes (EN)
Applies to every report of completed or in-progress changes: state the repo name up front. Especially important when juggling multiple repositories (e.g. company vs personal) where writing to the wrong one has real consequences.