scverse / scverse/scverse.github.io
Find a better place for our contributors guide than linking to scanpy one
Open
@Zethson is already working on this.
Since Aug 23, 2026.
- Dominant language
- SCSS
- Stars
- 4
- Forks
- 11
- Avg merge
- 12h 9m
- Merged PRs (30d)
- 42
Description
Currently, we link to the scanpy one. Should we have it on our main page somewhere? Is there any better spot that feels more "scverse-wide"?
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.
Assessment
This issue has not been assessed yet.