diff --git a/.github/dependabot.yml b/.github/dependabot.yml index 8fa8add81..1d27a290c 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -9,8 +9,8 @@ updates: versioning-strategy: increase rebase-strategy: "disabled" commit-message: - prefix: "[INFRA] prod -" - prefix-development: "[INFRA] dev -" + prefix: "chore(deps)" + prefix-development: "chore(deps-dev)" reviewers: - process-analytics/pa-collaborators @@ -23,6 +23,6 @@ updates: open-pull-requests-limit: 2 rebase-strategy: "disabled" commit-message: - prefix: "[INFRA] gha -" + prefix: "chore(gha)" reviewers: - process-analytics/pa-collaborators diff --git a/.github/workflows/pr-metadata-checks.yml b/.github/workflows/pr-metadata-checks.yml new file mode 100644 index 000000000..6c3e4f079 --- /dev/null +++ b/.github/workflows/pr-metadata-checks.yml @@ -0,0 +1,14 @@ +name: Check Pull Request Metadata +on: + pull_request_target: + # trigger when the PR title changes + types: [opened, edited, reopened] + +jobs: + pr-title: + runs-on: ubuntu-22.04 + permissions: + pull-requests: write # post comments when the PR title doesn't match the "Conventional Commits" rules + steps: + - name: Check Pull Request title + uses: bonitasoft/actions/packages/pr-title-conventional-commits@v2 diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2b53468eb..732893b0f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -10,7 +10,7 @@ There are many ways to contribute: - updating the theme & the styling of the site - improving the content of the site -- submitting bug reports in the [Github Issues](https://github.com/process-analytics/process-analytics.dev/issues/new) +- submitting bug reports in the [GitHub Issues](https://github.com/process-analytics/process-analytics.dev/issues/new) - improving the README ## Code and documentation changes guidelines @@ -23,12 +23,12 @@ For all contributions, please respect the following guidelines: 3. Do not commit changes to files that are irrelevant to your feature or bugfix (eg: `.gitignore`). -7. Open a [GitHub Pull Request](CONTRIBUTING.md#open-a-pull-request) with your patches. (**1** pull request = **1** feature or bug) +4. Open a [GitHub Pull Request](CONTRIBUTING.md#open-a-pull-request) with your patches. (**1** pull request = **1** feature or bug) We will review your contribution and respond as quickly as possible. Keep in mind that this is an open source project, and it may take us some time to get back to you. Your patience is very much appreciated. -8. If this is your 1st Pull Request, sign the [Contributor License Agreement](CONTRIBUTING.md#sign-the-contributor-license-agreement) +5. If this is your 1st Pull Request, sign the [Contributor License Agreement](CONTRIBUTING.md#sign-the-contributor-license-agreement) -9. Be willing to accept criticism and work on improving your code. +6. Be willing to accept criticism and work on improving your code. **Working on your first Pull Request?** You can learn how from this *free* series [How to Contribute to an Open Source Project on GitHub](https://app.egghead.io/playlists/how-to-contribute-to-an-open-source-project-on-github) @@ -75,7 +75,7 @@ Finally, go to GitHub and [make a Pull Request](https://help.github.com/articles For the title, follow the directives of the Pull Request template. Add a screenshot of the rendering of your examples/bpmn-file. -:warning: ​We care about quality. So your PR won't be merged until all tests pass. +**⚠️** We care about quality. So your PR won't be merged until all tests pass. ### Sign the Contributor License Agreement @@ -113,4 +113,4 @@ A PR can only be merged into master by a maintainer, if all of these conditions * It is passing CI. * It has been approved by at least two maintainers. If it was a maintainer who opened the PR, only one extra approval is needed. * It has no requested changes. -* It is up to date with current master. \ No newline at end of file +* It is up-to-date with current master.