Open lucascolley opened 4 days ago
I wasn't sure about these things (especially allcontributors) because it seemed to require access to the full data-apis organization, and I wasn't clear what that entailed. You should get feedback from @rgommers on this.
yeah, these are not high priority at all, I just thought it would be useful to keep track of them in an issue somewhere.
I'll try to make it to one of the community meetings, maybe we can discuss then.
I already enabled all-contributors when this repo was set up. Pixi sounds great, Codecov sounds fine too (as long as it's the config that doesn't comment but just adds the CI job entry with a link).
Pre-commit: sure, if you like it, go for it - you're doing most of the work here after all. As long as it's not mandatory and not hardcoded into the Pixi config preferably, because that will make it unusable for me. I'm happy for CI to fail and fix it up, or for pre-commit to add an extra auto-fix commit to my PR.
Pre-commit: sure, if you like it, go for it - you're doing most of the work here after all. As long as it's not mandatory and not hardcoded into the Pixi config preferably, because that will make it unusable for me.
Okay great, that's the request I was looking for. Currently, pixi run lint
installs pre-commit locally, but I understand that that is too workflow-prescriptive (I just punted on fixing it until somebody asked).
Codecov sounds fine too (as long as it's the config that doesn't comment but just adds the CI job entry with a link).
Sounds good - please could one of you go to https://app.codecov.io/gh/{your-username}/array-api-extra/new and add the CODECOV_TOKEN
secret?
Done:
pre-commit
without installing it (if requested?)pixi run tests
(https://github.com/scientific-python/specs/pull/324)