Hi, I'm not sure where to put that question, as it happens to me with both the API github and the character sheets github. Anyway. For months now, after my pull requests are merged, my clone repository still shows that it is some commit ahead of the Roll20 repository, although I didn't commit anything to my repository. Before this happened, after a pull request merge, I was just behind on some commits, so I fetched the Roll20 version, and then merged it into master, and all was fine. If I do that these days, my repository becomes a mess, and next pull request, it tries to re-commit my previously merged commits. The best way I found to deal with the current situation is to perform a git reset --hard of my repository to the Roll20 repository. That doesn't feel right, and in particular, that means I cannot commit anything before my pull requests get merged and then my repository is forced reset. So, the question are: Why? Why does the pull request merge leave me with some commits not counted as merged? Should I do something on my side after the pull request merge? Should I change the way I do my pull requests? (and why did it work for years before?) What would be a better way to synchronize back to Roll20 repository?