BUG REPORT: Failed Status checks getting removed after commit from the GitHub Action[bot]


All the previous Pull Requests checks are removed whenever there is an commit from the GitHub Action[bot].

1. there are  two failed checks before the commit from the GitHub Action[bot]

2. These  two failed checks  are removed after  the commit from the GitHub Action[bot]

Ideally, both of these failed Checks should still be present after the committ from the GitHub Action[bot]. However, these previous checks are getting disappeared when there is a committ from the GitHub Action[bot]

. This is the URL of the Pull Request where I tested this use-case


I have a few summary here for your reference:

1. When push some new changes to the to the source branch (github.head_ref) of a opened PR, the pull_request.synchronize event occurs and triggers a new workflow (check suite) to run with the latest commit (github.sha). In the Checks section, it only lists the checks from the latest check suite for the latest commit.
2. In the workflow run, if a step will make a event occur with GITHUB_TOKEN to authenticate, it will prevent the new workflow from running. Like ethomson mentioned in this ticket.
3. The action cla-assistant/github-action will push some new changes to the source branch with GITHUB_TOKEN to authenticate, the new workflow will be prevented from running, it will be skipped. So have no checks are listed for the latest commit in the Checks section.

So I think this is not a bug.

Hi @brightran, thank you for giving a detailed explanation. 

I understand that the new workflow will be prevented from running when there is a push which is the pull_request.synchronize event from the GitHub_Action authenticated as GITHUB_TOKEN. 

However, if the GitHub Action won’t be able to trigger the workflow then ideally, the checks section from the previous commit (check_suite),  shouldn’t also be removed/updated whenever there is a commit from the GitHub Action right ?.  

Thanks for your feedback.

GitHub takes your suggestions very seriously, and the suggestions are very helpful for improving GitHub.
I recommend you directly share your suggestion here. That will allow you to directly interact with the appropriate engineering team, and make it more convenient for the engineering team to collect and categorize your suggestions.

Hi @brightran I also created a similar issue regarding this and @ibakshay pointed me so I closed it.

I’m having pretty much the same issue, would you recommend us both filling out the feedback form?

Hi @dellow, I have already sent the feedback form reporting this issue and I will post the response from the GitHub team here. 

@ibakshayPerfect, thanks.

1 Like

Hi @brightran, I have raised this issue in GitHub like you suggested, however, unfortunately, I still haven’t heard anything from GitHub side.  

@dellow, Do you have any new developments/updates which you would like to share on this issue? that will be great :)).

@ibakshayNot exactly. I asked the question on the Github repo for the action I used and was sent to an issue that explains the situation regardless of whether you use the action or not: https://github.com/stefanzweifel/git-auto-commit-action/issues/38

Not exactly a resolution. Could really do with Github looking into this. Surely this is quite a large usecase for actions?

okay, thank you for the update @dellow  :)