forked from oppia/oppia
-
Notifications
You must be signed in to change notification settings - Fork 0
47 lines (44 loc) · 1.39 KB
/
oppiabot.yml
File metadata and controls
47 lines (44 loc) · 1.39 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
40
41
42
43
44
45
46
47
name: Oppiabot
on:
merge_group:
types:
- checks_requested
- destroyed
issues:
types:
- labeled
pull_request_target:
branches:
- develop
- release-*
permissions: read-all
concurrency:
group: ${{ github.workflow }}-${{ github.event_name }}-${{
github.event.pull_request.number || github.event.merge_group.head_ref
|| github.ref || github.run_id }}
cancel-in-progress: true
jobs:
oppiabot:
name: Verify CLA
runs-on: ubuntu-22.04
if: ${{ github.event_name != 'merge_group' || github.event.action != 'destroyed' }}
permissions:
issues: write
pull-requests: write
checks: write
statuses: write
steps:
- name: Checkout repository so that local actions can be used
uses: actions/checkout@v4
- name: Merge develop branch into the current branch
uses: ./.github/actions/merge
- name: Github Actions from Oppiabot
# Since we control the oppia/oppiabot repository, we can safely
# run the latest version of its code automatically. This is generally
# not a safe practice for dependencies we do not control.
uses: oppia/oppiabot@master
with:
repo-token: ${{secrets.GITHUB_TOKEN}}
sheets-cred: ${{ secrets.SHEETS_CRED }}
sheets-token: ${{ secrets.SHEETS_TOKEN }}
cla-sheet-id: ${{ secrets.SPREADSHEET_ID }}