MetOffice / MetOffice/simulation-systems
Update working practice section
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 57
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Include instructions which are mandatory for a developer covering things such as:
- Help needed to identify a SciTech reviewer (contact SSD team if it is not obvious)
- PR is not assigned for code review (Check if the PR still in DRAFT mode)
- Code Review delays (Release deadline approaching, but CR has not completed the review. Set a Milestone so this can be captured in weekly project reviews)
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
Locate the repository's working practice section and read the surrounding guidance before editing. Add the three requested mandatory practices: finding a SciTech reviewer, checking whether an unassigned PR is still in DRAFT, and recording code-review delays with a milestone; done means all three are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100