Changelog: August 19, 2026 - #61
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 19edd616da
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
|
||
| **GHES repositories as a Whitebox scan source**: On-prem users can now select a GitHub Enterprise Server repository as the source for a Whitebox scan. Previously only repos from other connected providers were available in the scan wizard. | ||
|
|
||
| **Glob patterns in author filters**: The `include.authors` and `exclude.authors` fields in `.hacktron/config.yaml` (and the equivalent org-wide settings) now accept glob patterns (`*`, `**`, `?`, ``) in addition to exact login names, using the same dialect already supported for branch and path filters. |
There was a problem hiding this comment.
Readers using this changelog to learn the supported author-filter syntax see an empty inline-code span after ?, so the supported {a,b} alternation form is omitted. Restore and properly escape that example so MDX renders the braces literally.
Useful? React with 👍 / 👎.
|
|
||
| **GHES repositories as a Whitebox scan source**: On-prem users can now select a GitHub Enterprise Server repository as the source for a Whitebox scan. Previously only repos from other connected providers were available in the scan wizard. | ||
|
|
||
| **Glob patterns in author filters**: The `include.authors` and `exclude.authors` fields in `.hacktron/config.yaml` (and the equivalent org-wide settings) now accept glob patterns (`*`, `**`, `?`, ``) in addition to exact login names, using the same dialect already supported for branch and path filters. |
There was a problem hiding this comment.
The August 3 update already states at line 48 that author include/exclude filters accept the same glob dialect, so this August 19 bullet presents an already-announced capability as newly available for a second time. Remove the duplicate or clarify the additional behavior that actually shipped on August 19 so the release chronology remains accurate.
Useful? React with 👍 / 👎.
2 participants
Documentation TODOs
These shipped features still need docs. The changelog links only to pages that already exist - add or update these, then link them:
/platform/repositories/azure-devopspage covers repo setup but not the personal account linking step.include.authors/exclude.authorsin.hacktron/config.yamland org-wide settings, with examples of*,**,?, and{a,b}patterns and the same safety limits that apply to branch/path globs.