usnistgov / oscal-tools

Tools for the OSCAL project

https://pages.nist.gov/oscal-tools/

34 stars 17 forks source link

Remove closed issues from triage board #55

Closed aj-stein-nist closed 2 years ago

aj-stein-nist commented 2 years ago

Committer Notes

This implements part of usnistgov/OSCAL#1302. See the following example workflow and runs associated with this test configuration.

Example issue with annotated automation: https://github.com/ImportantFederalAgencyTest/remove-project-card-test/issues/12 Successful workflow run creating the issue: https://github.com/ImportantFederalAgencyTest/remove-project-card-test/actions/runs/2463769565 Successful workflow run closing the issue: https://github.com/ImportantFederalAgencyTest/remove-project-card-test/actions/runs/2463777371

IMPORTANT:

[ ] Did I or did a project owner properly configured the COMMIT_TOKEN secret and it has at least repo:public_repo permissions?
[x] Did I or did a project owner configure triage board for this project to have a new done column with automation to correctly move closed issues and merged PRs for the triage board before merging this request?

All Submissions:

[x] Have you selected the correct base branch per Contributing guidance?
[x] Have you set "Allow edits and access to secrets by maintainers "?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you squashed any non-relevant commits and commit messages? [instructions]
[x] Do all automated CI/CD checks pass?

By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.

Changes to Core Features:

~Have you added an explanation of what your changes do and why you'd like us to include them?~
~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.~

aj-stein-nist commented 2 years ago

NOTE: I don't have admin access to this repo so I can't add a COMMIT_TOKEN secret, but I am guess there isn't one based on the existing other GitHub Actions workflow files that are already there (and we don't commit sources back to this repo).