PR Process for Entities Team Drafted by Severin & Shahriar on the following process for PR´s: Goals: Merge code ASAP, not letting it languish
- When creating PRs, Assign it to yourself & wait to make sure github actions run lint and unit tests successfully before assigning reviewers. a) If tests don’t run automatically, dev must run them manually before assigning reviewers.
- Assign 2 reviewers
- Send a message in the registries-Entities rocketchat channel, tagging the 2 reviewers & including a link to the PR a) Reviewers can refuse due to load b) Team can suggest others
- Only the person starting a conversation can resolve it.
- PRs must be looked at by reviewers within 24hrs of receieving the PR.
- Last reviewer must squash and merge.
PR-Process Assets Team
- @mention the reviewers on rocket
- chat and include a link to the PR
- It should be reviewed within an hour
- We've been reviewing in 5-10 minutes
PR Process for Team Relationships
- Assign any no. of reviewers
- At least two assignees must approve
- Communicate in RocketChat in channel "relationships-developers"