Fix GitHub PR action and adjust AI policy#1215
Merged
NeffIsBack merged 2 commits intomainfrom Apr 23, 2026
Merged
Conversation
Marshall-Hallenbeck
approved these changes
Apr 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR should:
It looks like to comment on PRs the token needs write privileges onto PRs from this repository. Therefore, the action now has a token in the context of the Pennyw0rth/NetExec repository and not the forked repository (difference of
pull_requestandpull_request_targetaccording to https://docs.github.com/de/actions/reference/workflows-and-actions/events-that-trigger-workflows#pull_request_target). Security wise this should be fine as we operate on a fixed set of strings that can be injected into the comment. There is not much input that is controlled by the user.I also adjusted the AI policy to more accurately reflect how I think about communication here. I don't mind when people use AI as an assistance for generating code (or content as well to some extent), but what I want to prevent is people just prompting AI and pasting the answers in Pull Requests or Issues. No one wants to communicate with a chat bot. Let me know what you think @mpgn, @Marshall-Hallenbeck.
Type of change
Insert an "x" inside the brackets for relevant items (do not delete options)
Setup guide for the review
N/A