build(deps): bump docker/login-action from 4.4.0 to 4.5.1 #111
This file contains hidden or 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: CLA Assistant | |
| on: | |
| issue_comment: | |
| types: [created] | |
| pull_request_target: | |
| # "reopened" lets maintainers force a fresh check (close/reopen) when a | |
| # stale failed run cannot be re-run (reruns reuse the old workflow snapshot). | |
| types: [opened, closed, synchronize, reopened] | |
| permissions: | |
| contents: write # write CLA signatures file | |
| pull-requests: write # comment on PRs | |
| statuses: write # set commit status check | |
| actions: write # re-run the failed CLA workflow after a "recheck" comment | |
| jobs: | |
| cla-check: | |
| name: CLA Check | |
| runs-on: ubuntu-latest | |
| # Skip PRs authored by bots and the repo owner (owner pushes directly to | |
| # main and is covered by the CLA as maintainer). Keyed on the PR author, | |
| # NOT github.actor: for pull_request_target the actor is whoever triggered | |
| # the event, so a maintainer reopening a contributor PR must not skip the | |
| # check. For comments, run only on signature/recheck comments. | |
| if: | | |
| (github.event_name == 'issue_comment' && (contains(github.event.comment.body, 'recheck') || contains(github.event.comment.body, 'I have read the CLA Document'))) || | |
| (github.event_name == 'pull_request_target' && github.event.pull_request.user.login != 'filipi86' && github.event.pull_request.user.login != 'dependabot[bot]') | |
| steps: | |
| - name: CLA Assistant | |
| uses: contributor-assistant/github-action@ca4a40a7d1004f18d9960b404b97e5f30a505a08 # v2.6.1 | |
| env: | |
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | |
| with: | |
| path-to-signatures: ".github/cla-signatures.json" | |
| path-to-document: "https://github.com/filipi86/drogonsec/blob/main/CLA.md" | |
| # Signatures are stored on a DEDICATED, UNPROTECTED branch. The bot | |
| # commits the signatures file with GITHUB_TOKEN, which cannot push to | |
| # main/staging/development (those are covered by the main-protection | |
| # ruleset, admin-bypass only). Writing to main here previously made the | |
| # check fail with "Repository rule violations found" even after signing. | |
| branch: cla-signatures | |
| allowlist: filipi86,bot*,*[bot] | |
| custom-notsigned-prcomment: | | |
| Thank you for your contribution to **DrogonSec**! | |
| Before we can merge this pull request, we need you to sign our **Contributor License Agreement (CLA)**. | |
| The CLA ensures you retain ownership of your contribution while granting the project the rights needed to maintain and develop DrogonSec — including any future enterprise products built on top of the open-source core. | |
| Please read the [CLA document](https://github.com/filipi86/drogonsec/blob/main/CLA.md) and sign by commenting below: | |
| ``` | |
| I have read the CLA Document and I hereby sign the CLA | |
| ``` | |
| This is a one-time action — once signed, all future PRs from your account are automatically approved. | |
| custom-allsigned-prcomment: | | |
| All contributors have signed the CLA. This check has passed. |