scikit-learn / scikit-learn/scikit-learn-release
Create automated issue when wheels failed on scikit-learn-release
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2
- Forks
- 4
- Avg merge
- 7h 51m
- Merged PRs (30d)
- 5
Description
With the wheels setup moving to scikit-learn-release, there are a few questions:
- which repo's CI is responsible for creating the automated issue. scikit-learn-release makes more sense since it will be running the full set of wheels.
- in which repo is the issue created? Maybe scikit-learn for higher visibility and consistency? For example, it is convenient to see all CI issues by saying
author:scikit-learn-botwith this Github search. We can use the scikit-learn-bot user token (needs to be added in this repo secrets). - how to share the code to create the automated issue in
scikit-learnandscikit-learn-release - other details I haven't thought about
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 resolving where the wheel-failure workflow belongs: scikit-learn-release or scikit-learn, and where the automated issue should be created. Review the existing CI setup and the scikit-learn-bot token approach; done means the repository ownership, shared implementation, and issue-creation details are decided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, shell
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100