docs(compatibility): clarify per-forge support and add metadata rows#287
Merged
barrettruth merged 1 commit intomainfrom Apr 17, 2026
Merged
docs(compatibility): clarify per-forge support and add metadata rows#287barrettruth merged 1 commit intomainfrom
barrettruth merged 1 commit intomainfrom
Conversation
Existing :h forge-compatibility table glossed over a few real gaps. Spell out PR/issue add/remove of reviewers, labels, assignees, and milestones so users can see exactly which mutations are wired up per backend, footnote the Codeberg assignee-removal limitation (`tea pulls edit` / `tea issues edit` lack `--remove-assignees`), mark GitLab release draft/prerelease as `n/a` rather than unsupported (the GitLab release model has no draft concept), and switch the footnote markers to numeric `(1)/(2)/(3)` per the canonical Vim help convention used in $VIMRUNTIME/doc/gui.txt.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
:h forge-compatibilityglossed over real gaps in the per-forge featurematrix. PR/issue metadata mutations (reviewers, labels, assignees,
milestone) were not broken out, so users could not tell which mutations
were wired up per backend; Codeberg's missing `--remove-assignees` flag
on `tea pulls edit` / `tea issues edit` was undocumented; GitLab
releases were marked unsupported for draft/prerelease when the GitLab
release model in fact has no such concept; and the footnote markers used
`*`, `†`, `‡` — `†` and `‡` only appear in
`$VIMRUNTIME/doc/digraph.txt` as digraph entries and are not used as
footnote markers anywhere else in the Neovim help corpus.
Solution
Spell out add/remove for reviewer, label, assignee, and milestone on PRs
and issues; footnote the Codeberg assignee-removal gap; mark GitLab
release draft/prerelease as `n/a` rather than `-`; switch footnote
markers to `(1)`/`(2)`/`(3)` per the canonical convention used in
`$VIMRUNTIME/doc/gui.txt` (and `pattern.txt`, `usr_11.txt`,
`tips.txt`, `visual.txt`); align value cells so footnoted rows match
the centered column convention used by every other row in the table.