Document module-list annotation convention in CONTRIBUTING.md - #341
Merged
Merged
Conversation
Adds a name/origin/status comment convention for entries in master-forge's pom.xml <modules> list, so the list stays a readable source of truth for where each plugin's code comes from and why a disabled one is disabled. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
3 tasks
1 task
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.
Summary
name/origin/statuscomment convention for each<module>entry inmaster-forge's rootpom.xml, so the<modules>list stays a self-contained source of truth for which plugins are managed, where their code comes from (fork vs. adopted branch), and why a disabled one is disabled.master-forge'spom.xml: (linked below once opened).Test plan
master-forgePR for consistency.