Add contributor workflow templates#23
Open
SalmonPlays wants to merge 3 commits into
Open
Conversation
Document focused contribution expectations and local browser verification.
Add a small template for reproducible bug reports.
Add a short checklist for browser verification and documentation updates.
Author
|
Small follow-up: this PR is intentionally limited to contributor workflow docs and GitHub templates. If the wording or scope does not match how this project handles contributions, I am happy to trim or adjust it, and it is also fine to close if these docs are not wanted. |
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.
This adds lightweight maintainer workflow files:
CONTRIBUTING.mdwith focused contribution expectations and local browser verification guidance.github/ISSUE_TEMPLATE/bug_report.mdfor reproducible bug reports.github/PULL_REQUEST_TEMPLATE.mdfor focused PR checksThis follows up on #22. I kept the change limited to documentation and GitHub templates; no application code or product data was changed.
Verification:
oss-signallocally before and after; the maintainer-readiness score improved from 21 to 39 for this repository clone