Skip to content

Repo assist PR result in Expected -- Waiting for status to be reported ... for ever #300

@halcwb

Description

@halcwb

When trying to merge a PR from repo-assist the required builds don't get triggered any more:

Image

The branch protection rules do not list the requirement to have successful repo-assist runs. There seems to be no good way out of this and the only way to go forward is to force merge which is very undesirable.

Repo-assist does run into failed runs:

All workflows
Filter workflow runs
Showing runs from all workflows
1,605 workflow runs
Repo Assist
Repo Assist #637: Issue comment informedica/GenPRES#237 (comment) edited by greptile-apps bot
28 minutes ago
2s
Repo Assist
Repo Assist #636: Pull request informedica/GenPRES#237 created by greptile-apps bot
33 minutes ago
1s
Repo Assist
Repo Assist #635: Issue comment informedica/GenPRES#237 (comment) created by greptile-apps bot
33 minutes ago
1s
Code Quality: PR #238
CodeQL #203: by github-actions bot
refs/pull/238/head
Mar 27, 10:08 PM GMT+1
50s
Code Quality: PR #237
CodeQL #202: by github-actions bot
refs/pull/237/head
Mar 27, 10:08 PM GMT+1
50s
Repo Assist
Repo Assist #634: Scheduled
master
Mar 27, 9:51 PM GMT+1
53s

though they are not listed as required under the branch protection.

I also noticed that in fact repo-assist had 2 exactly the same commits for this pr:

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions