Skip to content

mb - CODEOWNER updates for personnel changes#1520

Open
mbdhs wants to merge 2 commits into
developfrom
mbdhs-patch-1
Open

mb - CODEOWNER updates for personnel changes#1520
mbdhs wants to merge 2 commits into
developfrom
mbdhs-patch-1

Conversation

@mbdhs

@mbdhs mbdhs commented Jul 1, 2026

Copy link
Copy Markdown
Collaborator

🗣 Description

Update the owner list to account for recent staff changes.

💭 Motivation and context

New supervisors need access to provide approvals for changes.

🧪 Testing

Github web says the file has no errors.

✅ Pre-approval checklist

  • This PR has an informative and human-readable title.
  • Changes are limited to a single goal - eschew scope creep!
  • All future TODOs are captured in issues, which are referenced in code comments.
  • All relevant type-of-change labels have been added.
  • I have read the CONTRIBUTING document.
  • These code changes follow cisagov code standards.
  • All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
  • Tests have been added and/or modified to cover the changes in this PR.
  • All new and existing tests pass.
  • Bump major, minor, patch, pre-release, and/or build versions as appropriate via the bump_version script if this repository is versioned and the changes in this PR warrant a version bump.
  • Create a pre-release (necessary if and only if the pre-release version was bumped).

✅ Pre-merge checklist

  • Revert dependencies to default branches.
  • Finalize version.

✅ Post-merge checklist

  • Create a release (necessary if and only if the version was bumped).

mbdhs added 2 commits July 1, 2026 09:26
updated owner list
Now with correct names
@mbdhs mbdhs requested review from dav3r, felddy, jsf9k and mcdonnnj as code owners July 1, 2026 13:42

@dav3r dav3r left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool by me, but I strongly encourage you to fill out the PR template every time. It doesn't take long, especially for simple PRs like this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants