David Sanders
David Sanders
Closes #46. Breaking change since it will unarchive any existing repos which don't have `archived: true` in their config.
Would be nice to be have an `archived` boolean option for repositories so that a repo can be archived with a change to `.permissions/config.yml`.
Would be great if Sheriff could automatically enable branch protection on `main` when it creates a repo. Ideally configurable, but even opinionated hardcoding would be nice. Refs: https://docs.github.com/en/rest/branches/branch-protection#update-branch-protection
Currently `electron-rebuild` uses a single `node-gyp` job (the default) so it can only use a single core. With multi-core systems (should be almost all these days) this leaves a lot...
It's useful to be able to change the capabilities for a client. I'm using `clangd` and there are capabilities I'd like to enable, such as [inline fixes for diagnostics](https://clangd.llvm.org/extensions#inline-fixes-for-diagnostics).
If trop gets confused due to a bug or humans applying labels, PRs can end up with both `backport/accepted ✅` and `backport/requested 🗳` on it. We should prevent these conflicting...
We should validate that a manual backport has release notes if the original PR had release notes. I can't think of a use case where they should differ either, so...
This one is strange and I can't quite figure it out, but I'm seeing `opencv-build` needing to be rebuilt a lot as I do things with `yarn`. It's version 0.1.3...
#### Description of Change Follow-up to #42052 to enforce those changes (no autolinks and escaping `{`). The new `.lint-roller.json` config and binary name changes are a result of making `@electron/lint-roller`...
#### Description of Change If "Electron Version" can be parsed by `semver` to a valid version on a new bug issue, and `${major}-x-y` exists as a label, add that label...