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
If I have a useful entry in my CODEOWNERS file like:
/my/old/library @mwachs5
and then later I delete the directory, or rename it to
/my/new/library
There is nothing that flags the line as being 'dead' now. Since there is a limit to the size of the CODEOWNERS file, this could become a problem.
Describe the solution you'd like
This cleaning action could delete the dead lines.
I'd prefer to make that decoupled from the deletion of invalid users, since in our organization we'd prefer to have control over reassignment when we realize that the file has become outdated.
Describe alternatives you've considered
The way GitHub currently reports if the user is no longer present at the organization, thereby makign the CODEOWNERS file invalid, is fine. Though, it seems like since it is actually changes to the codebase (because files are handled by the repo) this could be done more synchronously with changes to the codebase.
a button one could click on the GUI for 'tell me whether this CODEOWNERS file meets certain criteria'
C/I check that prohibits invalidating changes to the CODEOWNERS file
Additional context
No response
The text was updated successfully, but these errors were encountered:
mwachs5
changed the title
Ability to flag lines that don't match code in the codebase anymore
Ability to flag/clean lines that don't match code in the codebase anymore
Oct 17, 2024
Is your feature request related to a problem?
If I have a useful entry in my CODEOWNERS file like:
/my/old/library @mwachs5
and then later I delete the directory, or rename it to
/my/new/library
There is nothing that flags the line as being 'dead' now. Since there is a limit to the size of the CODEOWNERS file, this could become a problem.
Describe the solution you'd like
This cleaning action could delete the dead lines.
I'd prefer to make that decoupled from the deletion of invalid users, since in our organization we'd prefer to have control over reassignment when we realize that the file has become outdated.
Describe alternatives you've considered
Additional context
No response
The text was updated successfully, but these errors were encountered: