-
Notifications
You must be signed in to change notification settings - Fork 0
62 lines (51 loc) · 1.74 KB
/
Copy pathwebextension.yml
File metadata and controls
62 lines (51 loc) · 1.74 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
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
name: Build and test
on:
push:
branches: [master]
pull_request:
workflow_dispatch:
jobs:
build:
runs-on: windows-latest
steps:
- uses: actions/checkout@v7
- uses: actions/setup-node@v7
with:
node-version: 22
- uses: actions/setup-dotnet@v6
with:
dotnet-version: 8.0.x
- name: Test the native messaging host
run: dotnet test BrowserGuard.Tests/BrowserGuard.Tests.csproj
# Run the stages separately rather than through "all", so that a failure
# points straight at the step it happened in. Lint pulls in the npm
# dependencies, which is why it comes first.
- name: Lint the extension
run: .\make.bat lint
shell: cmd
working-directory: webextensions
- name: Test the extension
run: .\make.bat test
shell: cmd
working-directory: webextensions
- name: Package
run: .\make.bat package
shell: cmd
working-directory: webextensions
# The signing key is not kept in the repository, so Edge signs with a
# throwaway key it generates. The resulting extension ID differs on every
# run, which makes this crx a build check rather than a deliverable.
# Release crx files for enterprise distribution are built locally with the
# designated key placed at pem\edge.pem.
- name: Pack crx
run: .\make.bat crx
shell: cmd
working-directory: webextensions
- uses: actions/upload-artifact@v7
with:
name: BrowserGuardEdge
if-no-files-found: error
path: |
webextensions/BrowserGuardEdge.zip
webextensions/BrowserGuardEdgeDev.zip
webextensions/BrowserGuardEdge.crx