Wiki - Add the below so we know how to update contributors in Readme
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
Note for the wiki page
Tebjan: the issue is just that you have to do one by one, after a merge, the next one has a conflict
so add, merge, add next...
Vaclav: What a saga! At least we learn something. Ok @tebjan. The PR needs to be closed and the created linked branch needs to be deleted, then it is going to work. My apology for causing this. There is an open issue so one doesn't have to do this drill https://github.com/all-contributors/all-contributors/issues/661
https://discord.com/channels/500285081265635328/1141714157415186435/1141772907354279956
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
Start with the wiki page and README contributor-update workflow described in the issue, then review the linked all-contributors issue for the referenced conflict and branch process. Done means the wiki explains how to update contributors after merges, including the noted one-by-one sequence and cleanup steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100