prometheus / prometheus/common
Scorecard supply-chain security CI broken
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 295
- Forks
- 367
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 18
Description
this CI has not succeeded in over 7 months. We should fix it or replace it with something that works.
Contributor guide
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 inspecting the repository's Scorecard supply-chain security CI configuration and its failed runs; no specific file or test is named in the issue. Determine why the CI has been failing for over seven months, then verify that the existing check succeeds or that a replacement security check runs successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100