CONTRIBUTING could be more concrete for new contributors
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
The repo looks interesting, but as a new contributor I would need a very practical guide: how to run backend/frontend locally, what checks to run before PR, where good first issues usually live, and how to test Agent-related changes without burning real API credits.
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 reviewing the existing CONTRIBUTING guidance and the repository's backend and frontend setup, pre-PR checks, first-issue locations, and Agent-related testing workflow. Document how contributors can run and validate these areas locally, including how to test Agent changes without using real API credits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience, documentation, testing
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100