electron/.github/config.yml

# Comment to be posted to on PRs from first time contributors in your repository
newPRWelcomeComment: |
  💖 Thanks for opening this pull request! 💖

  ### Semantic PR titles

  We use [semantic commit messages](https://github.com/electron/electron/blob/main/docs/development/pull-requests.md#commit-message-guidelines) to streamline the release process. Before your pull request can be merged, you should **update your pull request title** to start with a semantic prefix.

  Examples of commit messages with semantic prefixes:

  - `fix: don't overwrite prevent_default if default wasn't prevented`
  - `feat: add app.isPackaged() method`
  - `docs: app.isDefaultProtocolClient is now available on Linux`

  ### Commit signing

  This repo enforces [commit signatures](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) for all incoming PRs.
  To sign your commits, see GitHub's documentation on [Telling Git about your signing key](https://docs.github.com/en/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key).
  
  ### PR tips

  Things that will help get your PR across the finish line:

  - Follow the JavaScript, C++, and Python [coding style](https://github.com/electron/electron/blob/main/docs/development/coding-style.md).
  - Run `npm run lint` locally to catch formatting errors earlier.
  - Document any user-facing changes you've made following the [documentation styleguide](https://github.com/electron/electron/blob/main/docs/styleguide.md).
  - Include tests when adding/changing behavior.
  - Include screenshots and animated GIFs whenever possible.

  We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

# Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge

# Comment to be posted to on pull requests merged by a first time user
firstPRMergeComment: >
  Congrats on merging your first pull request! 🎉🎉🎉
Create config.yml 2017-08-16 18:54:10 +00:00			`# Comment to be posted to on PRs from first time contributors in your repository`
Update config.yml 2017-08-16 19:04:34 +00:00			`newPRWelcomeComment: \|`
			`💖 Thanks for opening this pull request! 💖`
feat: Allow testing of single spec modules (#11409) * :wrench: ES6 for the spec * :construction_worker: Allow testing of single modules * :heart: Implement feedback * :memo: Add a testing doc * :memo: Link to it * :memo: Cleanup 2017-12-28 11:18:33 +00:00
chore: mention signed commit requirement (#43406) chore: mentioned signed commit requirement 2024-08-23 13:52:33 +00:00			`### Semantic PR titles`

docs: Update Branch Name (#31106) * docs: Update CI Badge Branch Name The CI badges were still pointing at builds for the master branch, which are stale since the rename to main. * docs: Update electron/electron Branch Name Update electron/electron branch name from master to main. * docs: Update electron/governance Branch Name Update electron/governance branch name from master to main. 2021-09-27 15:35:56 +00:00			`We use [semantic commit messages](https://github.com/electron/electron/blob/main/docs/development/pull-requests.md#commit-message-guidelines) to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix.`
summarize semantic commit requirements (#12665) * summarize semantic commit requirements * move semantic commit details into contributing docs * keep those messages short 2018-05-02 14:47:26 +00:00
			`Examples of commit messages with semantic prefixes:`

			- `fix: don't overwrite prevent_default if default wasn't prevented`
			- `feat: add app.isPackaged() method`
docs: fix broken link to commit message guidelines (#13233) * docs: fix broken link to commit message guidelines * Fix another broken links 2018-06-16 00:43:03 +00:00			- `docs: app.isDefaultProtocolClient is now available on Linux`
summarize semantic commit requirements (#12665) * summarize semantic commit requirements * move semantic commit details into contributing docs * keep those messages short 2018-05-02 14:47:26 +00:00
chore: mention signed commit requirement (#43406) chore: mentioned signed commit requirement 2024-08-23 13:52:33 +00:00			`### Commit signing`

			`This repo enforces [commit signatures](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) for all incoming PRs.`
			`To sign your commits, see GitHub's documentation on [Telling Git about your signing key](https://docs.github.com/en/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key).`

			`### PR tips`

summarize semantic commit requirements (#12665) * summarize semantic commit requirements * move semantic commit details into contributing docs * keep those messages short 2018-05-02 14:47:26 +00:00			`Things that will help get your PR across the finish line:`
add typing cat to first PR comment (#11964) * add typing cat to first PR comment * update cat URL 2018-02-19 23:45:14 +00:00
docs: Update Branch Name (#31106) * docs: Update CI Badge Branch Name The CI badges were still pointing at builds for the master branch, which are stale since the rename to main. * docs: Update electron/electron Branch Name Update electron/electron branch name from master to main. * docs: Update electron/governance Branch Name Update electron/governance branch name from master to main. 2021-09-27 15:35:56 +00:00			`- Follow the JavaScript, C++, and Python [coding style](https://github.com/electron/electron/blob/main/docs/development/coding-style.md).`
Create config.yml 2017-08-16 18:54:10 +00:00			- Run `npm run lint` locally to catch formatting errors earlier.
docs: Update Branch Name (#31106) * docs: Update CI Badge Branch Name The CI badges were still pointing at builds for the master branch, which are stale since the rename to main. * docs: Update electron/electron Branch Name Update electron/electron branch name from master to main. * docs: Update electron/governance Branch Name Update electron/governance branch name from master to main. 2021-09-27 15:35:56 +00:00			`- Document any user-facing changes you've made following the [documentation styleguide](https://github.com/electron/electron/blob/main/docs/styleguide.md).`
Create config.yml 2017-08-16 18:54:10 +00:00			`- Include tests when adding/changing behavior.`
Update config.yml 2017-08-16 19:04:34 +00:00			`- Include screenshots and animated GIFs whenever possible.`
docs: fix broken link to commit message guidelines (#13233) * docs: fix broken link to commit message guidelines * Fix another broken links 2018-06-16 00:43:03 +00:00
Update config.yml 2017-08-16 19:04:34 +00:00			`We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.`
Create config.yml 2017-08-16 18:54:10 +00:00
			`# Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge`

			`# Comment to be posted to on pull requests merged by a first time user`
			`firstPRMergeComment: >`
			`Congrats on merging your first pull request! 🎉🎉🎉`