Fix: Use PAT so that next workflows can be triggered. #144
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
WHY
So there were two issues with the older update
https://github.com/peter-evans/create-pull-request/blob/main/docs/concepts-guidelines.md#triggering-further-workflow-runs
The workaround suggested is to use a PAT. Earlier there were security concerns but now. it's safer as we have fine-grained personal access token.
How to use
Who can run
Only USERS or Collaborators would be able to run https://github.com/nwtgck/actions-merge-preview/blob/develop/src/main.ts#L25
How to setup PAT (with minimal access):
https://github.com/settings/tokens
select repo
add these permission to token
Add token to your repository settings.
Tested & Working: ankit16-19#15
Checklist
sbt scalafmtAll
Run (and optionallysbt scalafmtSbt
)Summary by CodeRabbit