Repository navigation
docs: add GitHub Issue and pull request templates - #5
Merged
Merged
Conversation
Signed-off-by: jiangxt2 <[email protected]>
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.
Pull request
What changes were proposed in this pull request?
Add four English Issue Forms for bug reports, feature requests, improvements, and documentation problems, an Issue chooser configuration, and a pull request template. Adapt Gravitino and Ray prompts to Pista, including Spark/JDK and target engine versions, sanitized reproductions, related issues, user-facing impact, and validation.
Why are the changes needed?
Pista has no standard Issue or PR templates. These prompts help contributors provide actionable reports and help reviewers understand the proposed change and its validation.
Related issues
Fixes #4
Does this PR introduce any user-facing change?
Contributors receive four Issue categories and a structured PR description after the templates are merged into the default branch. Blank issues remain available, existing labels are reused, and the chooser links to the existing security policy.
How was this patch tested?
The following static checks passed with Python 3.14.8:
python3 -B scripts/check_language.pypython3 -B scripts/check_markdown.pypython3 -B scripts/check_public_content.pypython3 -B scripts/check_public_license.pyLocal YAML parsing and static review confirmed unique form names and field IDs, required flags, existing labels, and the PR sections. Live GitHub form rendering has not been verified.