Repo: Add issue forms and issue labeler workflow DRAFT #1028
+125
−0
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
Vercel Previews Deployed
|
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.
Description
This requires that repo Settings > General > Features > Issues is enabled. I do not have permissions to view Settings.
Jira: CE-1027
Community users are already creating docs issues in this repo.
This PR adds an issue template with a product pick list and an issue labeler workflow that runs when an issue is created or updated.
The issue labeler workflow applies a product label based on the product checked in the issue form. The product select list contains "Other product" and "No product" as choices. Those trigger a "Triage" label. I set "Terraform" as the default selected product since TF seems to have the most issues created by community users. I cannot have "Select..." or a blank value as list entry b/c it counts as a selected value (GH feature request). Validation is limited to required or not required.
Benefit: Automatic triage. users must choose a product when creating an issue. HashiCorp employees still use existing internal processes to create tickets.
Note: Individual product repos should modify their new issue chooser to point to web-unified-docs for opening docs issues. Refer to the Terraform new issue chooser for an example.
Architecture
New
.github/ISSUE_TEMPLATEdirectory to house the YAML for the issue forms.docs.yml: Docs issue form. Selecting a product from the Product drop-down is required.config.yml: 1) prevents a blank issue form. Since there are no links to external repos, the issue form opens when the user clicks the New Issue button in the GH web UI..github/workflowsAdd
label-issues.yml, which uses GHA Advanced Issue Labeler from Red Hat Plumbers. The label config file for the workflow is.github/advanced-issue-labeler.yml. The issue label does not need to exist in the repo prior to running the workflow. The workflow creates the label if it does not exist, but does not add a color to the label. I created entries for all the products in case we decide to use this repo for all product docs issues in the future.User flow:
Example screens
Screenshots from the implementation in my personal fork of web-unified-docs.
Docs issue form