I can see it now. Five years from now I'll be writing full-time. All my dreams came true. And then at the end of the day, I sit down to rebase this PR I just opened and attempt, yet again, to get reviews from the 11 teams that are codeowners.
Yes this is a programming joke.
Yes this is a programming joke.
November 6, 2025 at 5:49 PM
I can see it now. Five years from now I'll be writing full-time. All my dreams came true. And then at the end of the day, I sit down to rebase this PR I just opened and attempt, yet again, to get reviews from the 11 teams that are codeowners.
Yes this is a programming joke.
Yes this is a programming joke.
#457536 python3Packages.langgraph-cli: 0.4.4 -> 0.4.5
#457527 workflows/check: run codeowners validator from trusted checkout
#457527 workflows/check: run codeowners validator from trusted checkout
November 2, 2025 at 12:05 AM
#457536 python3Packages.langgraph-cli: 0.4.4 -> 0.4.5
#457527 workflows/check: run codeowners validator from trusted checkout
#457527 workflows/check: run codeowners validator from trusted checkout
workflows/check: run codeowners validator from trusted checkout
https://github.com/NixOS/nixpkgs/pull/457527
#security
https://github.com/NixOS/nixpkgs/pull/457527
#security
November 1, 2025 at 12:44 PM
workflows/check: run codeowners validator from trusted checkout
https://github.com/NixOS/nixpkgs/pull/457527
#security
https://github.com/NixOS/nixpkgs/pull/457527
#security
[Backport release-25.05] workflows/check: run codeowners validator from trusted checkout
https://github.com/NixOS/nixpkgs/pull/457529
#security
https://github.com/NixOS/nixpkgs/pull/457529
#security
November 1, 2025 at 12:44 PM
[Backport release-25.05] workflows/check: run codeowners validator from trusted checkout
https://github.com/NixOS/nixpkgs/pull/457529
#security
https://github.com/NixOS/nixpkgs/pull/457529
#security
This week has been about self-contained Ruby applications, GitHub codeowners validation, a Ruby version manager and a reverse proxy with load balancing and WAF built-in.
www.seachess.net/bulletins/20...
www.seachess.net/bulletins/20...
2025-W40
This week has been about self-contained Ruby applications, GitHub codeowners validation, a Ruby version manager and a reverse proxy with load balancing and WAF built-in.
www.seachess.net
October 5, 2025 at 7:42 AM
This week has been about self-contained Ruby applications, GitHub codeowners validation, a Ruby version manager and a reverse proxy with load balancing and WAF built-in.
www.seachess.net/bulletins/20...
www.seachess.net/bulletins/20...
`CODEOWNERS files must be under 3 MB in size` wtf
October 2, 2025 at 1:31 PM
`CODEOWNERS files must be under 3 MB in size` wtf
Hmm. I think the most important bits are having a pool of issues with a sufficiently wide difficulty range (probably could reuse the tidy-dev-day tags?) and having enough helpers to get people unstuck / advise on the right solution. It’s “easier” if codeowners are around too if you can manage it
September 21, 2025 at 1:11 PM
Hmm. I think the most important bits are having a pool of issues with a sufficiently wide difficulty range (probably could reuse the tidy-dev-day tags?) and having enough helpers to get people unstuck / advise on the right solution. It’s “easier” if codeowners are around too if you can manage it
#441224 gnomeExtensions.systemd-manager: 18 -> 19
#441222 golds: 0.7.8 -> 0.8.1
#441220 sd-switch: 0.5.5 -> 0.6.0
#441219 limine: 9.6.5 -> 9.6.6
#441217 ci/OWNERS: assign `pkgs/build-support/teleport` to teleport codeowners
#441216 evcc: 0.207.5 -> 0.207.6
#441222 golds: 0.7.8 -> 0.8.1
#441220 sd-switch: 0.5.5 -> 0.6.0
#441219 limine: 9.6.5 -> 9.6.6
#441217 ci/OWNERS: assign `pkgs/build-support/teleport` to teleport codeowners
#441216 evcc: 0.207.5 -> 0.207.6
September 9, 2025 at 12:05 AM
#441224 gnomeExtensions.systemd-manager: 18 -> 19
#441222 golds: 0.7.8 -> 0.8.1
#441220 sd-switch: 0.5.5 -> 0.6.0
#441219 limine: 9.6.5 -> 9.6.6
#441217 ci/OWNERS: assign `pkgs/build-support/teleport` to teleport codeowners
#441216 evcc: 0.207.5 -> 0.207.6
#441222 golds: 0.7.8 -> 0.8.1
#441220 sd-switch: 0.5.5 -> 0.6.0
#441219 limine: 9.6.5 -> 9.6.6
#441217 ci/OWNERS: assign `pkgs/build-support/teleport` to teleport codeowners
#441216 evcc: 0.207.5 -> 0.207.6
now how do I rollout CODEOWNERS files for 36 repos in a gh org? Idea is to automate adding reviewers to all PR’s.
I have half baked idea involving setting gh teams as codeowners - better than naming individual users as PR reviewers (following ETC principle).
But.. are teams just an abstraction?
I have half baked idea involving setting gh teams as codeowners - better than naming individual users as PR reviewers (following ETC principle).
But.. are teams just an abstraction?
a cartoon of a girl falling into the water with netflix written in the corner
ALT: a cartoon of a girl falling into the water with netflix written in the corner
media.tenor.com
September 4, 2025 at 4:26 AM
now how do I rollout CODEOWNERS files for 36 repos in a gh org? Idea is to automate adding reviewers to all PR’s.
I have half baked idea involving setting gh teams as codeowners - better than naming individual users as PR reviewers (following ETC principle).
But.. are teams just an abstraction?
I have half baked idea involving setting gh teams as codeowners - better than naming individual users as PR reviewers (following ETC principle).
But.. are teams just an abstraction?
When working in a team, controlling who reviews, approves, and merges code is just as important as writing good code. GitHub’s CODEOWNERS file, repository permissions, and teams (groups) provide a structured way to enforce accountability and maintain code quality.
devtoolhub.com/github-codeo...
devtoolhub.com/github-codeo...
GitHub CODEOWNERS & Permissions: Best Practices with Teams
When working in a team, controlling who reviews, approves, and merges code is just as important as writing good code. GitHub’s CODEOWNERS file, repository per
devtoolhub.com
August 20, 2025 at 3:02 PM
When working in a team, controlling who reviews, approves, and merges code is just as important as writing good code. GitHub’s CODEOWNERS file, repository permissions, and teams (groups) provide a structured way to enforce accountability and maintain code quality.
devtoolhub.com/github-codeo...
devtoolhub.com/github-codeo...
見てる: "renovate automerge 運用と CODEOWNERS 運用をいかに両立させるか" https://zenn.dev/kimuchan/articles/9152895c1761a9
August 20, 2025 at 5:04 AM
見てる: "renovate automerge 運用と CODEOWNERS 運用をいかに両立させるか" https://zenn.dev/kimuchan/articles/9152895c1761a9
I've released a new GitHub Action that merges PRs automatically if all files changed have the same code owner (using CODEOWNERS) as the submitter, something that surprisingly GitHub can't do on its own.
https://github.com/marketplace/actions/codeowners-automerge
https://github.com/marketplace/actions/codeowners-automerge
Codeowners automerge · Actions · GitHub Marketplace · GitHubInstagramTikTokTwitch
Automerges PRs from code owners that change only owned code
github.com
July 25, 2025 at 8:12 PM
I've released a new GitHub Action that merges PRs automatically if all files changed have the same code owner (using CODEOWNERS) as the submitter, something that surprisingly GitHub can't do on its own.
https://github.com/marketplace/actions/codeowners-automerge
https://github.com/marketplace/actions/codeowners-automerge
Anyone has experience with complex PR checks in #github ?
I have a usecase of a more complex codeowners/required Reviewer logic for a big project.
(1 reviewer from Group A, 1 from group B, and 2 reviews from any group)
(For specific branches also a review from group C)
(Other Branch only […]
I have a usecase of a more complex codeowners/required Reviewer logic for a big project.
(1 reviewer from Group A, 1 from group B, and 2 reviews from any group)
(For specific branches also a review from group C)
(Other Branch only […]
Original post on phpc.social
phpc.social
July 7, 2025 at 11:01 PM
Anyone has experience with complex PR checks in #github ?
I have a usecase of a more complex codeowners/required Reviewer logic for a big project.
(1 reviewer from Group A, 1 from group B, and 2 reviews from any group)
(For specific branches also a review from group C)
(Other Branch only […]
I have a usecase of a more complex codeowners/required Reviewer logic for a big project.
(1 reviewer from Group A, 1 from group B, and 2 reviews from any group)
(For specific branches also a review from group C)
(Other Branch only […]
Effiziente Verwaltung von CODEOWNERS-Dateien in GitHub-Organisationen: Ein umfassender Leitfaden
https://dasgeld.co/posts/EEB77F1E-4E5C-4163-B8F0-6FF967ECE1D8
https://dasgeld.co/posts/EEB77F1E-4E5C-4163-B8F0-6FF967ECE1D8
July 7, 2025 at 1:43 AM
Effiziente Verwaltung von CODEOWNERS-Dateien in GitHub-Organisationen: Ein umfassender Leitfaden
https://dasgeld.co/posts/EEB77F1E-4E5C-4163-B8F0-6FF967ECE1D8
https://dasgeld.co/posts/EEB77F1E-4E5C-4163-B8F0-6FF967ECE1D8
why is CODEOWNERS a single file somewhere far of that's a pain to edit and not like, a comment at the top of the file (you know, the way people used to manually track this stuff before git), or even (gasp) at the function level?
June 25, 2025 at 2:37 AM
why is CODEOWNERS a single file somewhere far of that's a pain to edit and not like, a comment at the top of the file (you know, the way people used to manually track this stuff before git), or even (gasp) at the function level?
…be laid on surgery tables (#17072) * Fixes unarmed attack tense shit (#17082) * Add bits requiring host/operations review to CODEOWNERS…
June 14, 2025 at 11:44 AM
…be laid on surgery tables (#17072) * Fixes unarmed attack tense shit (#17082) * Add bits requiring host/operations review to CODEOWNERS…
The field in the project is especially cool since it let's us annotate issues with a number of the `sx` usages impacted by taking on the work in a particular area (basically codeowners) and is updating daily as the migration is ongoing.
June 2, 2025 at 6:31 PM
The field in the project is especially cool since it let's us annotate issues with a number of the `sx` usages impacted by taking on the work in a particular area (basically codeowners) and is updating daily as the migration is ongoing.
“CODEOWNERS files must be under 3 MB in size”
I feel like there’s a story behind this limitation
I feel like there’s a story behind this limitation
May 29, 2025 at 4:36 PM
“CODEOWNERS files must be under 3 MB in size”
I feel like there’s a story behind this limitation
I feel like there’s a story behind this limitation
📦 timoschinkel/codeowners-cli 1.6.0
A cli interface for the codeowners library
🔗 https://github.com/timoschinkel/codeowners-cli
A cli interface for the codeowners library
🔗 https://github.com/timoschinkel/codeowners-cli
May 28, 2025 at 1:09 PM
📦 timoschinkel/codeowners-cli 1.6.0
A cli interface for the codeowners library
🔗 https://github.com/timoschinkel/codeowners-cli
A cli interface for the codeowners library
🔗 https://github.com/timoschinkel/codeowners-cli
Script to check CODEOWNERS files in all repositories of a github-organisation https://lobste.rs/s/woyndc ##python ##devops ##vcs
GitHub - sigio/github-audit-org-codeowner: Audit CODEOWNERS files in all repositories of a github-organisation
Audit CODEOWNERS files in all repositories of a github-organisation - sigio/github-audit-org-codeowner
github.com
May 27, 2025 at 3:40 PM
Script to check CODEOWNERS files in all repositories of a github-organisation https://lobste.rs/s/woyndc ##python ##devops ##vcs
Півдня мучався з CODEOWNERS, 🤬
а в нас стара версія GitLab де цю фічу що мені треба поки не завезли 🤣
а в нас стара версія GitLab де цю фічу що мені треба поки не завезли 🤣
May 23, 2025 at 3:27 PM
Півдня мучався з CODEOWNERS, 🤬
а в нас стара версія GitLab де цю фічу що мені треба поки не завезли 🤣
а в нас стара версія GitLab де цю фічу що мені треба поки не завезли 🤣
Work repo shared with 100 app teams. Codeowners set per team. Sr Eng opens MR for their app. Deletes a file under my app.
Asks me for approval via MR.
Open review. Won't approve as you delete my file.
They delete the review and escalate to my director lol.
Asks me for approval via MR.
Open review. Won't approve as you delete my file.
They delete the review and escalate to my director lol.
May 18, 2025 at 6:27 PM
Work repo shared with 100 app teams. Codeowners set per team. Sr Eng opens MR for their app. Deletes a file under my app.
Asks me for approval via MR.
Open review. Won't approve as you delete my file.
They delete the review and escalate to my director lol.
Asks me for approval via MR.
Open review. Won't approve as you delete my file.
They delete the review and escalate to my director lol.
Github has a bunch of tools for managing pull requests. You can set up branch protection and assign reviews to specific people; the CODEOWNERS file defines SMEs for specific sections #writethedocs
May 6, 2025 at 9:39 PM
Github has a bunch of tools for managing pull requests. You can set up branch protection and assign reviews to specific people; the CODEOWNERS file defines SMEs for specific sections #writethedocs
@bagder at $dayjob we have a CODEOWNERS file that specifies a github team as a codeowner.
When you create a non-draft PR, or switch a draft PR to a non-draft (the button is called "ready for review"), it adds the team as a reviewer.
As a result, everyone in the team sees the PR in their […]
When you create a non-draft PR, or switch a draft PR to a non-draft (the button is called "ready for review"), it adds the team as a reviewer.
As a result, everyone in the team sees the PR in their […]
Original post on mstdn.io
mstdn.io
April 28, 2025 at 6:56 AM
@bagder at $dayjob we have a CODEOWNERS file that specifies a github team as a codeowner.
When you create a non-draft PR, or switch a draft PR to a non-draft (the button is called "ready for review"), it adds the team as a reviewer.
As a result, everyone in the team sees the PR in their […]
When you create a non-draft PR, or switch a draft PR to a non-draft (the button is called "ready for review"), it adds the team as a reviewer.
As a result, everyone in the team sees the PR in their […]