docs: the changelog fragment cites bare #109
Maintainer ruling on the issue-number collision raised in the PR body. CONTRIBUTING's rule is "cite the issue or PR — (#96)", and fragments are assembled into CHANGELOG.md verbatim, so a fragment is the one place the convention is actually load-bearing. `forgejo#109` links on neither forge and would seed a second citation spelling in every future fragment. The prose distinction stays where it earns its keep: PR bodies and review comments still write forgejo#N, because that is where a reader has both numbering schemes in front of them at once.
This commit is contained in:
parent
ab29ee78fb
commit
25d10b084d
1 changed files with 2 additions and 2 deletions
|
|
@ -1,4 +1,4 @@
|
|||
### Added
|
||||
|
||||
- `rig forgejo-runner install|status|remove` registers a Forgejo Actions runner against an instance, jobs in containers on the box's own dockerd (forgejo#109)
|
||||
- The template registry can be served from any forge — `RIG_TEMPLATES_HOST` (forgejo#109)
|
||||
- `rig forgejo-runner install|status|remove` registers a Forgejo Actions runner against an instance, jobs in containers on the box's own dockerd (#109)
|
||||
- The template registry can be served from any forge — `RIG_TEMPLATES_HOST` (#109)
|
||||
|
|
|
|||
Loading…
Reference in a new issue