-
Notifications
You must be signed in to change notification settings - Fork 80
41 lines (34 loc) · 1.42 KB
/
guard-debug-workflow.yml
File metadata and controls
41 lines (34 loc) · 1.42 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
# HOW TO USE THIS WORKFLOW FOR BRANCH TESTING
#
# GitHub only shows workflow_dispatch workflows that exist on the default branch
# (master), but when you trigger them manually you can choose which branch to
# run against — GitHub will use the workflow file from that branch.
#
# Steps to test a workflow on your feature branch:
# 1. In your branch, replace the contents of this file with the workflow you
# want to test (keep the `workflow_dispatch` trigger so it stays triggerable).
# 2. Push your branch.
# 3. Go to Actions → "Debug Workflow (replace me in your branch)" → "Run workflow".
# 4. Select your branch from the dropdown and click "Run workflow".
#
# The contents of this file on master are intentionally left as a no-op stub.
# Do NOT merge your debug changes back to master.
name: Debug Workflow (replace me in your branch)
on:
# Manual trigger for testing
workflow_dispatch:
permissions:
contents: read
jobs:
test-local:
runs-on: [small, default-config]
steps:
- name: Harden the runner (Audit all outbound calls)
uses: step-security/harden-runner@fa2e9d605c4eeb9fcad4c99c224cee0c6c7f3594 # v2.16.0
with:
egress-policy: audit
- uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4.3.1
# Test the published action
# - name: New CDS Action
# uses: [fill this in on new branch]
# with: [fill this in on new branch]