-
Notifications
You must be signed in to change notification settings - Fork 31
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
Git history inconsistencies #60
Comments
Perhaps we can just create new PRs and merge them into |
Yikes! This is probably my fault. I might have force-pushed the |
It could’ve been anyone, really. It may have already been that way when you created #53. Regardless of how it happened, we thankfully have the PR history here to identify what changes need to be re-added. |
I'm leaning toward adding those PRs one-by-one, so their separate purposes are in separate PRs still. (Also, being frank, it's a little easier) |
Looking back at the PR history, these have all been addressed. |
I should have looked at #53 more carefully. There is something quite wrong with the history of our
modular
branch in this repo. The commits PRs #41, #42, #43, and #50 are all missing in the history of that branch and as a result they are no longer in the master branch of this repo either. I'm not sure at what point this happened and I'm not sure what to do about it, but I'll try to come up with a suggestion shortly.The text was updated successfully, but these errors were encountered: