ml-opensource / ml-opensource/Playbook
Contributing guide
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- No language data
- Stars
- 16
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Things that could/should be in there:
- Reporting Issues / Making PRs
- Git Flow
- Reviews
- README, CHANGELOG update
- Dependency Managers - Carthage (archive..) / CocoaPods/ SPM
- Tags, Releases
- More?
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
Review the repository's README and CHANGELOG, then identify where a contributing guide should live. Use the checklist as the required scope: issue and pull request workflow, Git Flow, reviews, release documentation, and Carthage, CocoaPods, and SPM guidance. Done means the guide covers these topics in a coherent, maintainable form.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100