Report when bot stops firing or runs into issues
A pull request for this has already been merged.
- #46 by @StanFromIreland — merged
- Dominant language
- Python
- Stars
- 6
- Forks
- 2
- Avg merge
- 9h 7m
- Merged PRs (30d)
- 2
Description
Currently there isn't any indication that the periodic execution in GitHub Actions stops working (beyond CVE IDs not getting assigned). Preferably somehow the automation would send an email to security@python.org if it stopped functioning so that PSRT folks are alerted. Very open-ended how this is implemented.
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
Start by reviewing the periodic GitHub Actions automation and how it currently signals CVE assignment failures. Define how a stopped or malfunctioning execution can be detected and how an email to security@python.org should be delivered; done means PSRT receives an alert for both conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100