Repository navigation
39 lines (36 loc) · 1.41 KB
/
Copy pathcla.yml
File metadata and controls
39 lines (36 loc) · 1.41 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
name: CLA
on:
issue_comment:
types: [created]
pull_request_target:
types: [opened, synchronize, reopened]
permissions:
actions: write
# write, not read: the action commits each signature to the branch below.
contents: write
pull-requests: write
statuses: write
jobs:
cla:
name: Check CLA
runs-on: ubuntu-24.04
# Only react to the signature sentence, or to pull request events. Note this
# workflow never checks out pull request code: `pull_request_target` runs
# with a writable token in the base repository context, so running a
# contributor's code here would hand them that token.
if: >-
github.event_name == 'pull_request_target' ||
(github.event.issue.pull_request != null &&
github.event.comment.body == 'I have read the CLA Document and I hereby sign the CLA')
steps:
- uses: contributor-assistant/github-action@ca4a40a7d1004f18d9960b404b97e5f30a505a08 # v2.6.1
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
path-to-document: https://github.com/labstack/pitot/blob/main/CLA.md
path-to-signatures: signatures.json
# Signatures live on their own branch. Storing them on main would put
# a bot commit into the release history and trigger a CI run plus an
# image publish every time somebody signs.
branch: cla-signatures
allowlist: vishr,dependabot[bot]