Some checks failed
Copilot Setup Steps / copilot-setup-steps (push) Failing after 1m1s
CI / test (ubuntu-latest, linux-x64) (pull_request) Failing after 1m8s
Copilot Setup Steps / copilot-setup-steps (pull_request) Failing after 31s
CI / test (macos-14, darwin-arm64) (pull_request) Has been cancelled
CI / test (windows-latest, windows) (pull_request) Has been cancelled
40 lines
1.4 KiB
YAML
40 lines
1.4 KiB
YAML
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: Check out repository
|
|
uses: actions/checkout@v4
|
|
|
|
- name: Install Nix
|
|
uses: cachix/install-nix-action@v31
|
|
with:
|
|
extra_nix_config: |
|
|
experimental-features = nix-command flakes
|
|
|
|
- name: Install flake dependencies
|
|
run: nix develop --accept-flake-config -c true
|