chore(deps): update google-github-actions/release-please-action action to v4 #378
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: "Pull Request auto-label" | |
| on: | |
| # Including 'on push' trigger, so that PRs touching the same files as push are checked for conflicts. | |
| # PR can be rebased (against main brnach) to resolve conflicts. | |
| push: | |
| branches: [ main ] | |
| pull_request_target: | |
| types: [ opened, synchronize ] | |
| jobs: | |
| conflicts: | |
| runs-on: ubuntu-latest | |
| permissions: | |
| contents: read | |
| pull-requests: write | |
| steps: | |
| - name: Update PRs with conflict labels | |
| uses: eps1lon/actions-label-merge-conflict@a4f3bd71c16f29387bb688d547800793b098f5cb # releases/2.1.0 | |
| with: | |
| dirtyLabel: "conflicts" | |
| #removeOnDirtyLabel: "PR: ready to ship" | |
| repoToken: "${{ secrets.GITHUB_TOKEN }}" | |
| commentOnDirty: "This pull request has conflicts with the base branch, please resolve those so that we can review the pull request." | |
| commentOnClean: "Conflicts have been resolved! 🎉 A maintainer will soon review the pull request." | |
| size: | |
| if: github.event_name == 'pull_request' || github.event_name == 'pull_request_target' | |
| permissions: | |
| issues: write | |
| pull-requests: write | |
| runs-on: ubuntu-latest | |
| steps: | |
| - uses: codelytv/pr-size-labeler@56f6f0fc35c7cc0f72963b8467729e1120cb4bed # v1.10.0 | |
| with: | |
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | |
| xs_label: 'size/xs' | |
| xs_max_size: 35 | |
| s_label: 'size/s' | |
| s_max_size: 75 | |
| m_label: 'size/m' | |
| m_max_size: 150 | |
| l_label: 'size/l' | |
| l_max_size: 300 | |
| xl_label: 'size/xl' | |
| message_if_xl: > | |
| This PR exceeds the recommended size of 300 lines (counting both additions & deletions). | |
| Kindly ensure that you are NOT addressing multiple issues in one PR. | |
| We recommend you to create atomic PRs which focus on a single change. |