Skip to content

Expected — Waiting for status to be reported on checks #1099

@CodexRaunak

Description

@CodexRaunak

Documenting for future fix

Image 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.

  1. Listening to push event
  2. Use SSH deploy key

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions