#50345: chore: wordsmith non-maintainer dependency change bot message
Description of Change
Add some guidance to the bot message when a non-maintainer contributes a PR that changes a disallowed file (dependency lockfiles, CI configs).
New message:
Hello @%AUTHOR%! It looks like this pull request touches one of our dependency or CI files, and per our contribution policy we do not accept these types of changes in PRs.
To move this PR forward, please:
- Revert the dependency/CI file changes from your branch. (e.g.
yarn.lock,.yarn/,.yarnrc.yml,.github/workflows/,.github/actions/)- Ensure your branch allows maintainer commits so a maintainer can push the necessary dependency changes on your behalf.
- Leave a comment letting reviewers know the dependency change is still needed.
For maintainers
To land this PR, push a verified commit to the contributor's branch with the required dependency/CI changes, then dismiss this review.
Checklist
- PR description included
Release Notes
Notes: none
Backports
No Backports Requested
This pull request doesn't have any backports requested or created for older release branches.
What are backports?
Backports are copies of changes made to the main branch that are applied to older release branches. They ensure that bug fixes and important changes are available in maintained older versions of Electron.
Semver Impact
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron