Insert a mention when clicking user's name in the timeline #1139
Workflow file for this run
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
name: Community PR notice | |
on: | |
workflow_dispatch: | |
pull_request_target: | |
types: | |
- opened | |
- reopened | |
jobs: | |
welcome: | |
runs-on: ubuntu-latest | |
name: Welcome comment | |
# Only display it if base repo (upstream) is different from HEAD repo (possibly a fork) | |
if: github.event.pull_request.base.repo.full_name != github.event.pull_request.head.repo.full_name | |
steps: | |
- name: Add auto-generated commit warning | |
uses: actions/github-script@v7 | |
with: | |
script: | | |
github.rest.issues.createComment({ | |
issue_number: context.issue.number, | |
owner: context.repo.owner, | |
repo: context.repo.repo, | |
body: `Thank you for your contribution! Here are a few things to check in the PR to ensure it's reviewed as quickly as possible: | |
- Your branch should be based on \`origin/develop\`, at least when it was created. | |
- The title of the PR will be used for release notes, so it needs to describe the change visible to the user. | |
- The test pass locally running \`./gradlew test\`. | |
- The code quality check suite pass locally running \`./gradlew runQualityChecks\`. | |
- If you modified anything related to the UI, including previews, you'll have to run the \`Record screenshots\` GH action in your forked repo: that will generate compatible new screenshots. However, given Github Actions limitations, **it will prevent the CI from running temporarily**, until you upload a new commit after that one. To do so, just pull the latest changes and push [an empty commit](https://coderwall.com/p/vkdekq/git-commit-allow-empty).` | |
}) |