docs: update hacking with explanation for exclamation point
Metadata
Current evaluation
Merged documentation update to the hacking guidelines. Added an explanation for using exclamation points in commit message headers. Approved by two reviewers with a +13/-3 line change across one file.
Suggested action: —
No scores available.
Issue body
- [ ] Have you followed the guidelines for contributing?
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [ ] Have you successfully run `tox`?
-----
Add explanation for when to use an exclamation point in a commit message header.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged documentation update to the hacking guidelines. Added an explanation for using exclamation points in commit message headers. Approved by two reviewers with a +13/-3 line change across one file. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged documentation update adding guidance on when to use an exclamation point in commit message headers. The change was successfully integrated into the main branch without additional comments. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #162 docs(HACKING): update commit message guidelines | starbase | merged | Merged updates to commit message guidelines in HACKING.rst for greater clarity. Approved by three reviewers, passed CI with 100% coverage, and modified three files. Minor commit type discussion did not block integration. | |
| #184 docs(HACKING): clarify commit header for merges | starbase | merged | Merged a documentation update to the HACKING file to clarify commit header guidelines for merges. The change was approved by a reviewer and successfully integrated. | |
| #346 docs(HACKING): add note about revert commits | starbase | merged | Merged documentation update to the HACKING guide. Added guidance on formatting revert commits using conventional commit standards. Approved by one reviewer, passed CI checks, and merged with a single line addition. | |
| #218 docs(HACKING): document branch names and changelog | starbase | merged | Merged documentation updates to the HACKING file covering branch naming conventions and changelog procedures. Approved by two reviewers, the change adds 92 lines to a single file. | |
| #225 docs(HACKING): add details on changelog convention | starbase | merged | Merged documentation update adding changelog convention details to the HACKING guide. Approved by two reviewers, passed CI checks, and subsequently upstreamed to the canonical/starbase repository. | |
| #4006 docs: update HACKING.md to recurse submodules | snapcraft | merged | Merged documentation update to HACKING.md instructing developers to recurse into submodules for spread tests. Approved by one reviewer and merged by maintainer @mr-cal, who dismissed unrelated test failures. | |
| #791 docs: update CONTRIBUTING.md | craft-application | merged | Merged after reviewer approval and passing CI checks. Updated CONTRIBUTING.md and removed HACKING.md. | |
| #349 style(HACKING): fix typo | starbase | merged | Merged a one-line typo fix in the HACKING file. Approved by one reviewer with passing CI checks. The change corrects a spelling error in the contributing guidelines. | |
| #910 Update HACKING.md | snapcraft | merged | Merged a documentation update to HACKING.md that removes an obsolete testing section and relocates it after dependency installation. The change was approved by a reviewer with a follow-up question. |