mozilla-services / mozilla-services/obs-common
README should cover how development works
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 13h 3m
- Merged PRs (30d)
- 7
Description
This comment and probably some other information about the dev workflow for this repository should get captured in the README:
https://github.com/mozilla-services/obs-common/pull/28#discussion_r1828122418
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 reading the repository README and the development-workflow discussion in pull request #28. Identify the comment's guidance and any directly related workflow information that is missing from the README. Done means the relevant development instructions are captured clearly in the README.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100