scverse / scverse/ecosystem-packages
If github action validating ecosystem packages fails, nobody gets notified
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39
- Forks
- 90
- Avg merge
- 10h 19m
- Merged PRs (30d)
- 9
Description
Opening a GitHub issue is probably the way to go.
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 locating the GitHub Actions workflow that validates ecosystem packages and reviewing how failures are currently surfaced. Trace a failing run and determine the expected notification path; done means a validation failure produces a notification, with a workflow check confirming the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100