-
Notifications
You must be signed in to change notification settings - Fork 32
41 lines (35 loc) · 1.57 KB
/
copilot-setup-steps.yml
File metadata and controls
41 lines (35 loc) · 1.57 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
name: "Copilot Setup Steps"
# Automatically run the setup steps when they are changed to allow for easy validation, and
# allow manual testing through the repository's "Actions" tab
on:
workflow_dispatch:
push:
paths:
- .github/workflows/copilot-setup-steps.yml
pull_request:
paths:
- .github/workflows/copilot-setup-steps.yml
jobs:
# The job MUST be called `copilot-setup-steps` or it will not be picked up by Copilot.
copilot-setup-steps:
runs-on: ubuntu-latest
# Set the permissions to the lowest permissions possible needed for your steps.
# Copilot will be given its own token for its operations.
permissions:
# If you want to clone the repository as part of your setup steps, for example to install dependencies, you'll need the `contents: read` permission. If you don't clone the repository in your setup steps, Copilot will do this for you automatically after the steps complete.
contents: read
# You can define any steps you want, and they will run before the agent starts.
# If you do not check out your code, Copilot will do this for you.
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Install fixpoint
uses: ./.github/actions/install-fixpoint
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
- name: Install Z3
uses: cda-tum/setup-z3@v1.6.6
with:
# Note: Using 4.12.1 for standard tests. vtock and lean-demo tests use 4.15.3
# to avoid hanging issues, but those run in separate CI jobs.
version: 4.12.1