This repository has been archived by the owner on Sep 21, 2023. It is now read-only.
Add Issue Triage automation to project for usnistgov/OSCAL#1209. #53
Conversation
This file contains 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
aj-stein-nist
added
the
Scope: CI/CD
Closed
7 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Committer Notes
This pull requests adds automation so that any new issue (and only new issues) will be added to this repository's Issue Triage board and its Needs Triage to initiate the triage process. This PR is part of a tracker issue for relevant repos in usnistgov/OSCAL#1209.
This has been tested in a dummy organization with example issues (one with no project board configured on creation, the other intentionally with the project assigned. If other test cases are needed, please advise. (Re the issue acceptance criteria, the
on: [opened]filter forissueswill most assuredly prevent this from being applied to existing issues.Project board: https://github.com/ImportantFederalAgencyTest/create-project-card-test/projects/1
Example Issue 1: ImportantFederalAgencyTest/create-project-card-test#1
Example Issue 1's GitHub Action run: https://github.com/ImportantFederalAgencyTest/create-project-card-test/actions/runs/2185526148
Example Issue 2: ImportantFederalAgencyTest/create-project-card-test#2
Example Issue 2's GitHUb Action run: https://github.com/ImportantFederalAgencyTest/create-project-card-test/actions/runs/2185661979
All Submissions:
"?
Changes to Core Features:
Have you written new tests for your core changes, as applicable?Have you included examples of how to use your new feature(s)?Have you updated all OSCAL website and readme documentation affected by the changes you made? Changes to the OSCAL website can be made in the docs/content directory of your branch.