fix(docs): sync vimdoc with current forge behavior#448
Merged
barrettruth merged 1 commit intomainfrom Apr 27, 2026
Merged
Conversation
The help file had drifted from the implemented command, compose, and template surfaces. Bring the docs back in line with the code and define the missing compose highlight defaults so the documented groups exist.
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
doc/forge.nvim.txthad drifted from the implemented command, compose, template, and config surfaces, and some documented compose highlight groups were not defined by default.Solution
Update the vimdoc to match the live behavior, document the missing PR edit and template-path details, and add default highlight links plus a focused spec for
ForgeComposeLabelandForgeComposeDraft.