docs: add contributing-plugins guide to docs-dev#6760
Open
netram75 wants to merge 1 commit into
Open
Conversation
Port the contributing-plugins section from docs-v1.0.x to docs-dev so the bleeding-edge docs include the plugin contribution guide. Update all internal links from /docs-v1.0.x/ to /docs-dev/ throughout both files. Refs pipe-cd#6679 Signed-off-by: netram75 <netram.24bcs10329@sst.scaler.com>
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.
What this PR does:
Adds the
contributing-plugins/section todocs-dev, which was missing entirely. Ported fromdocs-v1.0.x/contribution-guidelines/contributing-plugins/with internal links updated to point todocs-devwhere those pages exist.Also fixes a broken link introduced in #6758, where
contributing.mdindocs-devlinks to../contributing-plugins/— that path had no target until now.Why we need it:
docs-devis the source for the next release. Plugin contributors reading the dev docs had no guide on how to build or contribute plugins.Which issue(s) this PR fixes:
Refs #6679
Does this PR introduce a user-facing change?:
docs-devcan now access the full plugin contribution guide.