ref: Remove unused requester field from parsed inputs#7169
Merged
Conversation
The `requester` field was parsed from the issue body in `detailsFromContext` but never consumed by any downstream module or workflow step. Remove the regex, the match call, and the field from the return object to reduce dead code.
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
1 participant
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.
Summary
requesterfield that was parsed from the issue body indetailsFromContextbut never consumed by any downstream module or workflow stepDetails
The
requesterfield was extracted via regex from the "Requested by: @username" line in publish issues, but no code actually reads it:process-end-state.jsonly destructures{ repo, version }from inputsupdate-issue.jsonly destructures{ version }from inputsrepo,merge_target,version,path,dry_run, andtargets— but neverrequester