New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] Investigate possible bug using since_last_remote_commit when force pushing changes. #303

Closed

3 tasks done

jackton1 opened this issue Jan 3, 2022 · 1 comment

Labels

bug

Member

jackton1 commented Jan 3, 2022

Is there an existing issue for this?

I have searched the existing issues

Does this issue exist in the latest version?

I'm using the latest release

Describe the bug?

Based on #301 there might be an intermittent bug which occurs when a new sha is forcefully pushed to a branch.

See: https://github.com/tj-actions/changed-files/runs/4687127870?check_suite_focus=true

To Reproduce

See: https://github.com/tj-actions/changed-files/runs/4687127870?check_suite_focus=true

What OS are you seeing the problem on?

all

Expected behavior?

This should use the last remote sha instead of raising an error

Relevant log output

No response

Anything else?

No response

Code of Conduct

I agree to follow this project's Code of Conduct

jackton1 added the bug label

Member Author

jackton1 commented Feb 1, 2022

Unable to replicate this bug would keep an eye out for any new occurrence

jackton1 closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment