Repository navigation
chore: issue forms, shared triage and stale workflows - #1574
Merged
Merged
Conversation
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
config.ymlthat disables blank issues and links to private security reporting, Discussions, docs and the website. The repo-levelISSUE_TEMPLATEoverrides the organization defaults, so the forms live here with Querya-specific fields.community.ymlcalls the shared workflows fromQueryaHub/.github: unlabeled new issues getneeds-triage; issues labeledneeds-infogo stale after 14 days and close after 7 more (PRs 30 + 14). Milestones,security,blocked,good first issueandhelp wantedare exempt, so roadmap issues are never touched.needs-triage,needs-info,stale,security,blockedalready created in the repo. Discussions enabled.Linked issue
None.
Checklist
dev/issues/new/chooseafter merge to the default branch