docs(HACKING): add details on changelog convention
Metadata
Current evaluation
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.
Suggested action: —
No scores available.
Issue body
- [x] Have you followed the guidelines for contributing?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] Have you successfully run `tox`?
-----
Refining changelog convention now that they are getting used in more projects.
source: https://github.com/canonical/craft-application/pull/377
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | 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. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged documentation update detailing changelog conventions for the HACKING guide. Changes were subsequently upstreamed to canonical/starbase to standardize practices across projects. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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. | |
| #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. | |
| #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. | |
| #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. | |
| #366 docs: add changelog | craft-application | merged | Merged documentation update adding a changelog for the 2.9.0 release. Approved by two reviewers, the change adds 93 lines across two files following starbase conventions. | |
| #226 docs: update hacking with explanation for exclamation point | starbase | merged | 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. | |
| #791 docs: update CONTRIBUTING.md | craft-application | merged | Merged after reviewer approval and passing CI checks. Updated CONTRIBUTING.md and removed HACKING.md. | |
| #5578 docs: update CONTRIBUTING.md | snapcraft | merged | Merged after approvals and passing CI. Updated CONTRIBUTING.md, removed HACKING.md, and reverted a redundant conf.py change. A reviewer noted a remaining README reference to HACKING.md requiring separate handling. | |
| #215 docs: add CONTRIBUTING.md | imagecraft | merged | Merged into main, replacing HACKING.md with CONTRIBUTING.md. Approved by reviewers and passed all CI checks. Maintainer suggested future content trimming, but the documentation update was successfully integrated. | |
| #2568 docs: consolidate on a simple HACKING.md | snapcraft | merged | Merged into master. Consolidates development setup and contribution guidelines into a single HACKING.md file for consistency and easier onboarding. Approved by a reviewer, passed CI checks, and integrated without impacting code coverage. |