You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been mulling over boosting our review process (#998, #985, #1005, and more).
Here's what I'm thinking:
We kick-off with a comment sporting a checkbox and easy-peasy instructions. A bot gets to tick this when the contributor's nailed all tasks, or a reviewer steps in to give it a nod.
We keep a CI/CD check yellow - a signal we're on standby, not in error mode - until the checkbox gets a tick.
Bonus: this special comment can be updated by the bot to give straightforward specific instructions.
This ensures that either the contributor's done their bit, or a reviewer's given it a thumbs up.
There's good stuff happening over at https://github.com/snyk/release-notes-preview - they're using a similar system for making commit messages chime with automatic changelog and releases.
Later on, our bot could step up - like ensuring devs have signed off on a DCO, or handling specific directives for crucial repo folders. For this, I'd go with a CI/CD reacting to PR changes, and invoking a homemade Go script we could nestle in misc/gh-action.
What do you think? Let's chew the fat over this.
The text was updated successfully, but these errors were encountered:
moul
changed the title
Proposal: Improving Review Process with Bot-Assisted Checkboxes
Proposal: improving review process with bot-assisted checkboxes
Jul 31, 2023
We've been mulling over boosting our review process (#998, #985, #1005, and more).
Here's what I'm thinking:
This ensures that either the contributor's done their bit, or a reviewer's given it a thumbs up.
There's good stuff happening over at https://github.com/snyk/release-notes-preview - they're using a similar system for making commit messages chime with automatic changelog and releases.
Later on, our bot could step up - like ensuring devs have signed off on a DCO, or handling specific directives for crucial repo folders. For this, I'd go with a CI/CD reacting to PR changes, and invoking a homemade Go script we could nestle in
misc/gh-action
.What do you think? Let's chew the fat over this.
The text was updated successfully, but these errors were encountered: