[Feature] since_last_passing_remote_commit

[Archie-Elvie]

Is this feature missing in the latest version?

• I'm using the latest release

Is your feature request related to a problem? Please describe.

I'm currently using this action to detect changes to our dockerfile that we use for dev and our CI/CD pipeline. Currently it will rebuild our image and upload it to the registry if the dockerfile has changed since last remote commit. However, if the workflow fails before the build can be uploaded, this change in dockerfile is not captured. Therefore the next remote commit that might fix the failed workflow might not have a dockerfile change and therefore the image rebuild will not take place and an old image will be used for testing.

Describe the solution you'd like?

A way to check if a file has been modified since the last passing remote commit. This should fix the issue stated above. Passing in this context is passing all enabled workflow checks.

Describe alternatives you've considered?

Current solution is a rule that disallows editing the workflows and dockerfile in the same remote commit, however other issues could arise (such as server failure) that this would not capture.

Anything else?

If anyone has a workaround for this that would work with the current version, that would be great. Let me know if you have any questions.

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Thanks for reporting this issue, don't forget to star this project to help us reach a wider audience.

[jackton1]

@Archie-Elvie I’ve updated the README highlighting the solution to solving this problem.

[Archie-Elvie]

@jackton1 That works great, thank you. Out of interest is there a reason to use tj-actions/branch-names@v5 instead of ${{ github.ref_name }}?

[jackton1]

@Archie-Elvie From my test it doesn't appear that ${{ github.ref_name }} is going to return a valid branch name always which is why tj-actions/branch-names@v5 is recommended.