digitalbazaar / digitalbazaar/github-workflow-shared-action-osv-scanner
Improve "OSV" issue label behavior.
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 1
- Avg merge
- 7m
- Merged PRs (30d)
- 15
Description
Some possible improvements for the forced "OSV" label for the created issue:
- Add option to use a different label name and default to "OSV".
- Document this label being used.
- Ideally the label could be optional, but that might be more difficult due to the code using that to find the issue to update.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the workflow configuration and the code path that uses the forced "OSV" label to find and update issues. Define how a configurable label name, documentation, and optional-label behavior should work, then verify that issue creation and updates still target the intended issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100