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.
Simple PR adding a
force-commit-sha
input.While the workaround proposed there (=relying on the CLI directly) actually works when you have to deal with
workflow_run
executions, it has at least one major downside.In case I want to keep the CLI version up to date, I need to either
Also,
workflow_run
seems the most secure/reliable way to deal with forked PR, but as stated on #78 the CLI uploader doesn't correctly handle that case. So adding the input would bring a nice workaround for issues like #33, #67 or #69 for instance.Another way to cover the case would be to update the
GitHubActionProvider
from the CLI uploader directly (like did there codacy/codacy-coverage-reporter#492), in order to manageworkflow_run
events, but I guess it would require way more than just the few lines added there.Feel free to suggest any updates (input name/description, etc).