Demo Describe Code Review With a Codeowners File

​

Where to add a CODEOWNERS file

• .github/CODEOWNERS (common and recommended)
• docs/CODEOWNERS
• CODEOWNERS at the repository root

1. Create .github/CODEOWNERS (or one of the other supported locations).

2. Example .github/CODEOWNERS contents:

*.js @alice-mcberry
index.html @sid-harth-1

• Any change to a .js file will automatically request @alice-mcberry as a reviewer.
• Any change to index.html will automatically request @sid-harth-1 as a reviewer.

​

Quick reference: common CODEOWNERS patterns

• Use @org/team-name for organization teams.
• Place more specific patterns above more general patterns (rules are matched top-to-bottom).

​

Test your CODEOWNERS configuration

• Create a new branch from main, for example: test-CODEOWNERS.
• Make a small change to a file that matches a pattern in your CODEOWNERS file.
• Commit the change and open a pull request targeting main.

// ==== GAME STATE =====
const gameState = {
  currentLevel: 1,
  score: 0,
  highScore: Number(localStorage.getItem('blockBusterHighScore')) || 0,
  lives: 3,
  isPaused: false,
  isGameRunning: false,
  balls: [],
  particles: [],
  bullets: [],
  activePowerups: [],
  powerups: {
    multiBall: { active: false, activationTime: 0 },
    megaPaddle: { active: false, activationTime: 0 },
    bulletMode: { active: false, activationTime: 0 }
  },
  bulletFireCounter: 0
};

const canvas = document.getElementById('gameCanvas');
const ctx = canvas.getContext('2d');

let paddle = {
  width: 100,
  height: 25,
  x: Math.max(0, (canvas.width / 2) - 50),
  speed: 8
};

​

Notes and gotchas

• Rules are processed top-to-bottom: place specific patterns before generic ones.
• Owners may be individual users (@username) or organization teams (@org/team-name).
• If a username or team does not exist (or the team is private and not accessible), GitHub cannot auto-request that owner.
• CODEOWNERS only affects new pull requests comparing against the default branch where the CODEOWNERS file resides. It does not retroactively update existing PRs.
• Consider combining CODEOWNERS with branch protection to require reviews from code owners: see GitHub branch protection settings.

​

Links and references

• About CODEOWNERS — GitHub Docs
• Configuring protected branches — GitHub Docs
• Managing teams — GitHub Docs