You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an issue that can sometimes occur with force-pushes. Git(Hub) is an eventually-consistent system, so when there is a force-push, we may clone faster than Git(Hub) has made the new commit available on the /pull/:number ref. The clone still succeeds (it just gets a previous state), but then we call the git diff --name-only <pr head sha> to see if we've made any restylings, with the <pr head sha> that we got from the GitHub API, which is more up to date than what we cloned, it says the commit does not exist (bad object).
There are a number of reasons that Restyled is impacted by this and other operations on the PR are not -- maybe they're silently happy to operate with a stale state (that seems bad), maybe they don't rely on the /pull/:number ref, or maybe operations within the GitHub ecosystem see git updates faster than the rest of us. Or, maybe they've implemented some kind of retry or other special handling.
I'm unlikely to work on fixing this right now, but would be happy to accept any patches for it. In the meantime I will write up a note in the wiki.
Hi there-
I'm having a problem with a Restyled Job
What I expected to happen:
The job to succeed like for other PRs in this repo.
What happened instead:
Configuration (if applicable):
N/A (it works or used to work on other changes)
The text was updated successfully, but these errors were encountered: