-
Notifications
You must be signed in to change notification settings - Fork 37
Open
Description
Documenting for future fix
This issue arised in PRs made via GiHub actions[bot] on the metadata repo. Upon checking this issue is discussed at peter-evans/create-pull-request/issues/48)
"It seems that any PRs that get created by the action will not trigger any actions waiting on a pull request event or push event". Therefore `validate-metadata` checks did't get trigger in the above.
This restriction by GitHub is to prevent any `accidental recursive` workflows.
Workarounds that are recommended by GitHub is to use a Personal Access Token and that way when we create PRs its identified by the user not the actions[bot] which will trigger the further workflows.
But there is another workaround using SSH (deploy keys) to push the pull request branch. This is arguably more secure than using a PAT because deploy keys can be set per repository. However, this method will only trigger on: push workflows.
Future Actions:
I tried implementation using SSH(Deploy Keys) which worked well. For now we are leaving it to the maintainer but in future when resolving the issue if needed we can reference the implementation of SSH given below.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels