Skip to content
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.

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

changeset points to outdated commit after force-pushed #91

Open
scarf005 opened this issue Jan 10, 2025 · 0 comments
Open

changeset points to outdated commit after force-pushed #91

scarf005 opened this issue Jan 10, 2025 · 0 comments

Comments

@scarf005
Copy link

scarf005 commented Jan 10, 2025

image

I apologize in advance that i cannot provide the link to the repo (happened in private repo).

Even after adding changeset and force-pushing (latest commit points at 90f5141167e927d66ecead5c2d877f6cc771f800), changeset bot doesn't pick up newer changes and still points to old commit ac575912d75a5bfd464ee0f33951a725a227768f

image
image

this makes the changeset bot to not pick changeset and incorrectly report as "no changeset found".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant