Status Check war reseted after Commit about add-and-commit

[EndBug]

This is intended behavior on GitHub's part: PR status checks always refer to the latest commit, so if you don't re-trigger CI on the automated commit it won't display any status checks

That's because otherwise an action could break your code and the status checks would still be successful

You need to either commit using a PAT, or re-trigger some the status checks you need either manually or via a workflow dispatch call to the API

[ernestoguimaraes]

Hey @EndBug ! thank you.

But one question:; I was testing with my friend yesterday. in the same scenario, If I ask him to Update the Branch, the status is not reset. The reset problem happens using GITHUB_TOKEN and now a GitHub App Token. The PAT is an option, however, using in a enterprise scenario, I will reach the PAT Threshold very fast.

[EndBug]

Maybe if you update the branch using the GitHub UI they just keep the previous result, since they "trust" the operation. I don't know exactly what the criteria is though 🙌🏻

I would suggest you allow your "test" workflows, the ones you require the status checks to be run for, to be run via workflow dispatches, then add a step using some action to send the dispatch via the GitHub API
There are a few actions on the marketplace you can use for that, this is one of them: https://github.com/marketplace/actions/workflow-dispatch

[ernestoguimaraes]

I was making some tests here and noticed something.
Before my workflow starts, my PR is attached to a commti Hash. As a need to make a Branch commit, It´s creating a new Hash.
Is there a way to make a commit and preserve the original Hash? I believe it´s Fast-Foward, right?

[EndBug]

I don't think it's possible, because the SHA of each commit is generated by git internals by hashing different info about the commit, including the SHA of the parent.
That makes it impossible to insert a commit in the history without modifying every commit down the line.
Even with fast-forward merges or rebases, the SHA of every subsequent commit is re-calcultated.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.