-
### Description
The codeowners support #10161 introduced in https://github.com/go-gitea/gitea/pull/24910 doesn't seem to support paths starting with `/`:
```
# works
docs/*.\\.md
# doesn't
/do…
-
This is a follow-up to #2320:
On e.g. #2582, Dependabot should not automatically add google/android-fhir group as reviewers to its PRs.
-
###### Desired state
Every repository in our orgs (ipfs, libp2p, multiformats, etc.) contains a `CODEOWNERS` file on the default branch which defines the default code owners - `*`. The defaults cod…
-
@robinv85 brought up this issue earlier.
To prevent contributors from making changes to code that was architected a certain way for a particular reason, and to allow the contributors and the person…
-
## Description
I'd like to validate CODEOWNERS files whenever they've been changed.
## Value
Breaking this automation by committing an invalid configuration can lead to review stagnation.
…
-
**Application Name**: Global - tools
**OS**: Windows 10 21H2
**CPU**: X64
**.NET Build Number**: dotnet-sdk-9.0.100-rc.1.24413.1
**App & Source checking at:** https://devdiv.visualstudio.com/DevDi…
-
The README or CONTRIBUTOR file should list how to get in touch with the maintainers of the project. This should preferably be using a method that can include any individual rather than linked to a spe…
-
In GitHub's CODEOWNERS docs it says that you can use email addresses (one or more) associated to your GitHub account to define the owner. The extension doesn't seem to support this.
https://help.gith…
neonb updated
5 years ago
-
I think adding a .github/CODEOWNERS file would be a good move.
Creating `.github/CODEOWNERS` would auto-request reviewers. For example:
```
# Request review by OpenRTX Expedition Force for all pull …
-
#### Reason/Context
In Modelina we have a similar setup (where each language, input and website has sub-codeowners) which I think makes sense to have in the CLI as well.
And that is: Each command…