You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/actions/prepare-test/action.yml
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@ name: "Prepare test"
2
2
description: Performs some preparation to run tests
3
3
inputs:
4
4
version:
5
-
description: "The version of the CodeQL CLI to use. Can be 'linked', 'default', 'nightly', 'nightly-latest', 'nightly-YYYYMMDD', or 'stable-vX.Y.Z"
5
+
description: "The version of the CodeQL CLI to use. Can be 'linked', 'default', 'toolcache', 'nightly', 'nightly-latest', 'nightly-YYYYMMDD', or 'stable-vX.Y.Z"
6
6
required: true
7
7
use-all-platform-bundle:
8
8
description: "If true, we output a tools URL with codeql-bundle.tar.gz file rather than platform-specific URL"
Copy file name to clipboardExpand all lines: .github/pull_request_template.md
+48-1Lines changed: 48 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,13 @@
1
-
<!-- For GitHub staff: Remember that this is a public repository. -->
1
+
<!--
2
+
For GitHub staff: Remember that this is a public repository. Do not link to internal resources.
3
+
If necessary, link to this PR from an internal issue and include further details there.
4
+
5
+
Everyone: Include a summary of the context of this change, what it aims to accomplish, and why you
6
+
chose the approach you did if applicable. Indicate any open questions you want to answer
7
+
during the review process and anything you want reviewers to pay particular attention to.
8
+
9
+
See https://github.com/github/codeql-action/blob/main/CONTRIBUTING.md for additional information.
10
+
-->
2
11
3
12
### Risk assessment
4
13
@@ -7,6 +16,44 @@ For internal use only. Please select the risk level of this change:
7
16
-**Low risk:** Changes are fully under feature flags, or have been fully tested and validated in pre-production environments and are highly observable, or are documentation or test only.
8
17
-**High risk:** Changes are not fully under feature flags, have limited visibility and/or cannot be tested outside of production.
9
18
19
+
#### Which use cases does this change impact?
20
+
21
+
<!-- Delete options that don't apply. -->
22
+
23
+
-**Advanced setup** - Impacts users who have custom workflows.
24
+
-**Default setup** - Impacts users who use default setup.
-**Test repository** - This change will be tested on a test repository before merging.
35
+
-**Unit tests** - I am depending on unit test coverage (i.e. tests in `.test.ts` files).
36
+
-**End-to-end tests** - I am depending on PR checks (i.e. tests in `pr-checks`).
37
+
-**Other** - Please provide details.
38
+
-**None** - I am not validating these changes.
39
+
40
+
#### If something goes wrong after this change is released, what are the mitigation and rollback strategies?
41
+
42
+
<!-- Delete strategies that don't apply. -->
43
+
44
+
-**Feature flags** - All new or changed code paths can be fully disabled with corresponding feature flags.
45
+
-**Rollback** - Change can only be disabled by rolling back the release or releasing a new version with a fix.
46
+
-**Other** - Please provide details.
47
+
48
+
#### How will you know if something goes wrong after this change is released?
49
+
50
+
<!-- Delete options that don't apply. -->
51
+
52
+
-**Telemetry** - I rely on existing telemetry or have made changes to the telemetry.
53
+
-**Dashboards** - I will watch relevant dashboards for issues after the release. Consider whether this requires this change to be released at a particular time rather than as part of a regular release.
54
+
-**Alerts** - New or existing monitors will trip if something goes wrong with this change.
55
+
-**Other** - Please provide details.
56
+
10
57
### Merge / deployment checklist
11
58
12
59
- Confirm this change is backwards compatible with existing workflows.
0 commit comments