vimcolorschemes / vimcolorschemes/worker
feat: Consider forks as valid repositories
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5
- Forks
- 0
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 4
Description
Currently, no forks have the opportunity to be featured on vimcolorschemes.com
As discussed in https://github.com/vimcolorschemes/vimcolorschemes/issues/287, forks could be considered as valid repositories as long as they respect certain conditions:
- Repository name is different than the original repository
- ... probably more coming once this is worked on
An example of a valid fork is: Iron-E/nvim-highlite
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 tracing how the worker currently decides which repositories can be featured, then review the linked discussion in vimcolorschemes/vimcolorschemes#287 and the Iron-E/nvim-highlite example. Define the complete fork-validation conditions before implementing them; done means valid forks can be featured without admitting repositories that violate those conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100