[go: up one dir, main page]

Skip to content

Allow adding a CODEOWNERS entry from a file/directory

This an actionable insight from the Code Review FY21-Q2 Category Maturity Scorecard research (insight).

Problem to solve

As a project lead, I want to manage CODEOWNERS entries from the files/directories themselves, so I can spend less time navigating between files.

During research, many participants attempted to “protect” a file from the file page itself. Specifically, they were trying to add a new CODEOWNERS entry for that file so that they could then enable Code Owner approvals. Most importantly, the goal they were looking for was: require approval for any changes to this file.

People intuitively perceive things as “objects.” So, in this case, it was natural for users to try to manipulate the file or its relationship from within the file itself (the object).

To reach the intended outcome, users will likely have to search for the documentation, read it, learn what they must to, and then come back to the UI. Ideally, the UI should be self-explanatory, or try to provide possible pathways for users to achieve their goals.

Intended users

Proposal

Because users intuitively navigated to the file that they were trying to “protect”, we can add a way for users to add a new CODEOWNERS entry from a file/directory.

image

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

No

Links / references