Browse code
feat(ci): initial workflow
Showing 1 changed files
1 | 1 |
new file mode 100644 |
... | ... |
@@ -0,0 +1,32 @@ |
1 |
+# This is a basic workflow to help you get started with Actions |
|
2 |
+ |
|
3 |
+name: CI |
|
4 |
+ |
|
5 |
+# Controls when the workflow will run |
|
6 |
+on: |
|
7 |
+ # Triggers the workflow on push or pull request events but only for the master branch |
|
8 |
+ push: |
|
9 |
+ branches: [ master ] |
|
10 |
+ pull_request: |
|
11 |
+ branches: [ master ] |
|
12 |
+ |
|
13 |
+ # Allows you to run this workflow manually from the Actions tab |
|
14 |
+ workflow_dispatch: |
|
15 |
+ |
|
16 |
+# A workflow run is made up of one or more jobs that can run sequentially or in parallel |
|
17 |
+jobs: |
|
18 |
+ # This workflow contains a single job called "build" |
|
19 |
+ build: |
|
20 |
+ # The type of runner that the job will run on |
|
21 |
+ runs-on: ubuntu |
|
22 |
+ container: nixos/nix |
|
23 |
+ |
|
24 |
+ # Steps represent a sequence of tasks that will be executed as part of the job |
|
25 |
+ steps: |
|
26 |
+ # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it |
|
27 |
+ - uses: actions/checkout@v2 |
|
28 |
+ |
|
29 |
+ # Runs a set of commands using the runners shell |
|
30 |
+ - name: Run a multi-line script |
|
31 |
+ run: | |
|
32 |
+ nix shell -c zig build |