mne-tools / mne-tools/mne-python
Switch doc building CI provider?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.5k
- Forks
- 1.6k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 100
Description
Thanks! OT, but I don't like a core service failing because a contributor must first configure something or is not logged in (as a side note, I've never been able to restart a job even though I am logged in, but I seem to have two accounts connected to my email, which is also very confusing). I suggest that we try to fix this on our side, or consider moving to a different service with better GitHub integration.
Originally posted by @cbrnr in https://github.com/mne-tools/mne-python/issues/13680#issuecomment-4554985188
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
No files, tests, or entry points are named. Start by locating the repository's current CI provider configuration and reviewing the reported login and job-restart failures. Done means establishing whether the service can be fixed or should be replaced, then documenting and implementing the agreed direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- ci-cd, devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100