Thanks @pono, There might be a common scenario to address here (because I don't recall a force push on our end): when one edits a file from GitHub's' web interface, it creates a branch in the form of user-patch-n . If that branch is deleted after it is merged (and it almost always is), the next time this happens from the same user, n will start back at 1. The result is, over time, multiple branches will have existed with the same name but different commits. This might be the cause, because we've done this. If it is the cause, this is likely to occur again.
On Thu, Sep 28, 2017, 16:24 Daniel Pono Takamori <p...@apache.org> wrote: > Looks like a forced update caused some problems. I've updated Gitbox > so it should be in sync now. > > On Thu, Sep 28, 2017 at 2:10 PM, Christopher <ctubb...@apache.org> wrote: > > Hi INFRA, > > > > Apache Fluo got an error message that prevented some commits from being > > pushed to a GitBox repo. We were able to push to GitHub, and they got > > automatically sync'd to GitBox, so we're not really sure what's up with > > that. > > > > Details at > > https://github.com/apache/fluo-website/pull/95#issuecomment-332949229 > > >
