generated from the-collab-lab/smart-shopping-list
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into new-feature
- Loading branch information
Showing
6 changed files
with
60 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
# CODEOWNERS file for TCL-75 Smart Shopping List | ||
# | ||
# What is this file? | ||
# This file helps automate the code review process by automatically assigning reviewers | ||
# to pull requests (PRs) and setting rules for PR approvals. | ||
# | ||
# How does it work? | ||
# 1. Automatic Reviewer Assignment: | ||
# - When a PR is opened, GitHub automatically assigns the mentors listed below as reviewers. | ||
# | ||
# 2. Review Requirements (set in GitHub branch protection rules, not in this file): | ||
# - Each PR needs at least 3 approvals to be merged: | ||
# a) 2 approvals from peer developers | ||
# b) 1 approval from a mentor (automatically assigned by this file) | ||
# | ||
# 3. Mentor Approval: | ||
# - At least one of the mentors listed below MUST approve the PR before it can be merged. | ||
# - This ensures experienced oversight on all code changes. | ||
# | ||
# How to request reviews: | ||
# 1. In GitHub: | ||
# - When opening a PR, manually request reviews from 2 peer developers. | ||
# - Mentors will be automatically assigned as reviewers. | ||
# | ||
# 2. In Slack: | ||
# - Use the following Slack reacji to notify team members: | ||
# a) :todo-tcl75-devs: - This will ping developers for a review | ||
# b) :todo-tcl75-mentors: - This will ping mentors for a review | ||
# - Using these reacji helps communicate review needs efficiently to the team | ||
# | ||
# Best Practice: | ||
# - Use both GitHub assignment and Slack notifications to ensure visibility and prompt reviews. | ||
# | ||
# Mentors for TCL-75 (automatically assigned and required for PR approval): | ||
* @ahsanatzapier @jendevelops @deeheber |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters