Skip to content

Conversation

@jalseth
Copy link
Member

@jalseth jalseth commented Oct 22, 2025

When a location is specified by the policy, the GitHub actions UI will now take the user directly to the source of the violation.


This builds on #1196.

This will allow outputters to point to the specific location that caused the
result to be created.

Signed-off-by: James Alseth <[email protected]>
@jalseth jalseth force-pushed the jalseth/refactor-github branch from 6133406 to 5740718 Compare October 22, 2025 22:29
@jalseth jalseth marked this pull request as ready for review October 22, 2025 22:36
@jalseth jalseth requested review from boranx and jpreese October 22, 2025 22:36
@jalseth jalseth force-pushed the jalseth/refactor-github branch 2 times, most recently from 64c91ab to 492c700 Compare October 22, 2025 23:24
When a location is specified by the policy, the GitHub actions UI will now
take the user directly to the source of the violation.

Signed-off-by: James Alseth <[email protected]>
@jalseth jalseth force-pushed the jalseth/refactor-github branch from 492c700 to 0214aa5 Compare October 22, 2025 23:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants