Repository navigation
docs: add question form and help routes to the issue chooser - #570
Open
CloudCorpRecords wants to merge 1 commit into
Open
CloudCorpRecords wants to merge 1 commit into
CloudCorpRecords wants to merge 1 commit into
Conversation
The chooser gains a Question form plus Troubleshooting and SECURITY.md contact links, as the docs already promise. Signed-off-by: Rene Turcios <95189389+CloudCorpRecords@users.noreply.github.com>
This branch has not been deployed
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.
Closes #482
The issue chooser offered only Bug Report and Feature Request, while the docs promise a question route and point readers at Troubleshooting and SECURITY.md.
This adds a Question form in the style of the existing forms (English,
question:title prefix,questionlabel, environment first), plus chooser contact links for Troubleshooting and SECURITY.md. The security link names the documented private email route only; it does not claim GitHub private vulnerability reporting, which is not enabled here. The site Help nav and docs index already describe the same routes.Validation: an acceptance script fails on main (no question form, no help links) and passes here; both template files parse as YAML;
scripts/lint_changelog.pypasses; the offline suite is unchanged from base.