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
You are an expert technical writer and product specialist for GitHub Advanced Security (GHAS) on GitHub Enterprise Server (GHES).
6
6
7
-
When asked to update this feature matrix for a new GHES version, follow this strict procedure:
7
+
When asked to update this Advanced Security feature matrix for a new GHES version, follow this strict procedure:
8
8
9
9
## 1. Research Phase
10
10
-**Identify the Version:** Determine the specific GHES version number requested (e.g., 3.16).
11
11
-**Consult Release Inventory:** Read the official start/end/docs/releasenote information for all versions at `End of life dates at: https://docs.github.com/en/enterprise-server/admin/all-releases#releases-of-github-enterprise-server`.
12
12
-**Consult Release Notes:** Read the official release notes at `https://docs.github.com/en/enterprise-server@<VERSION>/admin/release-notes`.
13
13
-**Specifics**
14
14
- CodeQL version included in the runner toolcache is located in this document: https://docs.github.com/en/enterprise-server@<VERSION>/admin/managing-code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance#provisioning-the-actions-for-code-scanning
15
-
- Secret Scanning pattern counts are easily discovered for the GHES VERSION by reading the latest comment in this gist: https://gist.github.com/felickz/9688dd0f5182cab22386efecfa41eb74
15
+
- Secret Scanning pattern counts are easily discovered for the GHES VERSION by running this script on the public docs for secret scanning pattern list: https://github.com/felickz/scripts/blob/main/pwsh/Count-SecretScanningPatterns.ps1
16
16
17
-
-**Inventory Features:** Look for changes in these specific areas:
17
+
-**Inventory Features:** Look for changes in these specific areas relating to GitHub Advanced Security:
- Administration (Security Configurations - only advanced security features or features with major security implications only)
23
+
- do not put security configuration setup for specific features under the feature section - keep the security configuration under Administration!
23
24
-**Check Dependencies:** Note any changes to setup requirements (Actions, Connect, etc.) for the Dependencies section.
24
25
25
26
## 2. Analysis Guidelines
@@ -28,7 +29,7 @@ When asked to update this feature matrix for a new GHES version, follow this str
28
29
- Explicitly check if existing features have moved from Preview to GA in this release.
29
30
-**Significance Filter:**
30
31
-**INCLUDE:** New functionality, major gaps addressed, major architectural changes, new versions, counts.
31
-
-**EXCLUDE:** Minor bug fixes, simple renames (e.g., "Generic" -> "Experimental"), or UI tweaks without functional impact.
32
+
-**EXCLUDE:** Minor bug fixes, new versions of existing langagues/framework support added (ex: Go 1.25 or Swift 6.1.2), simple renames (e.g., "Generic" -> "Experimental"), or UI tweaks without functional impact.
32
33
33
34
## 3. Matrix Update Rules
34
35
-**New Column:** Always add a new column for the new version in *every* table, even if there are no specific changes for that table.
@@ -37,5 +38,5 @@ When asked to update this feature matrix for a new GHES version, follow this str
37
38
38
39
## 4. Pull Request & Output Instructions
39
40
When generating the Pull Request description or summary of changes:
40
-
-**List Omissions:** Explicitly list any features you saw in the release notes but decided *not* to include in the matrix. This helps the reviewer confirm if they should be added.
41
+
-**List Omissions:** Explicitly list any advanced security / security features you saw in the release notes but decided *not* to include in the matrix. This helps the reviewer confirm if they should be added.
41
42
-**Rendered Link:** Include a link to the rendered view of the Markdown file so the reviewer can easily visualize the table columns.
0 commit comments