processing / processing/processing-contributions
improve developer experience of repo
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8
- Forks
- 8
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 3
Description
edits to this repo happen rarely enough, that it's easy to forget specific characteristics of it. documentation would help, as would tests on the scripts, as well as a pull request template that reminds the contributor to run the tests, and to test the update contributions workflow on the contributor's fork.
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
No specific files or tests are named. Start by reviewing the repository documentation, scripts, and update contributions workflow to identify the current contributor steps and testing gaps. Done means the documentation, script tests, and pull request template all address the requested contributor guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience, documentation, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100