I have an action (triggered on all pushes) which runs a particular coverage tool and generates a badge which I have included in my README. I use this action after the coverage tool to commit the new badge (with the new percentage). I also have a number of other actions that are also triggered on pushes.
What's great is that github seems to be intelligent enough that pushing the new badge does not trigger these actions a second time. However, when I push to a branch that has a pull request already open, this new push of the badge is taken as the latest commit and results in multiple pending checks instead being shown indefinitely on the pull request instead of using the checks from the original commit. This basically means having to close and reopen the pull request. And generally being unable to push to branches with open PRs.
My question is whether there is any way of getting around this? It doesn't seem like other people have experienced the same problem. Thanks!
I have an action (triggered on all pushes) which runs a particular coverage tool and generates a badge which I have included in my README. I use this action after the coverage tool to commit the new badge (with the new percentage). I also have a number of other actions that are also triggered on pushes.
What's great is that github seems to be intelligent enough that pushing the new badge does not trigger these actions a second time. However, when I push to a branch that has a pull request already open, this new push of the badge is taken as the latest commit and results in multiple pending checks instead being shown indefinitely on the pull request instead of using the checks from the original commit. This basically means having to close and reopen the pull request. And generally being unable to push to branches with open PRs.
My question is whether there is any way of getting around this? It doesn't seem like other people have experienced the same problem. Thanks!