Repository navigation
docs: add a contributing guide - #32
Merged
Merged
Conversation
Signed-off-by: igorjs <2278164+igorjs@users.noreply.github.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
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
New contributors had no single page to tell them where a change goes or how a release ships. The README also read as if the optional hooks install line works today, and it won't until a playbook release carries the hooks archive.
What Changed
CONTRIBUTING.mdwith a table mapping each kind of change (skills and commands, the plugin version, the marketplace listing, authoring guides, model and effort policy) to the file or folder you edit.intents.jsoncheck against aplaybookbinary. It also explains why a skill names an intent in plain words instead of a binary subcommand.Signed-off-by, the 1000 line limit, no dashes) and the release steps, from the version bump PR through the signedvX.Y.Ztag and GitHub release.playbook-hooksinstall line only applies once a playbook release ships the hooks archive.