-
Notifications
You must be signed in to change notification settings - Fork 92
Commit reconciliation request #668
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
Conversation
…re cascading of rename to triangle.columns_label.
…st jupyter notebooks.
…r copy that had the previous ordering. Closes casact#667.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #668 +/- ##
=======================================
Coverage 85.00% 85.00%
=======================================
Files 85 85
Lines 4883 4883
Branches 626 626
=======================================
Hits 4151 4151
Misses 522 522
Partials 210 210
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
FYI, this is happening because I squashed the last PR. This lumps all the intermediate commits into a single one, keeping the commit history clean on the main. any fork showing they are ahead in commits doesn't actually contain any new changes. you can click sync fork to rebase. |
Hey @kennethshsu, I've got that weird situation going on where I'm getting notified that my fork is 20-something commits ahead even though almost all these changes were merged in yesterday.
Could you please do me a favor and approve this PR (it has a mostly meaningless 1-character change), but let me merge and close it myself? I think the last time I did this, the issue cleared up, but if it doesn't, I'll do a hard reset on my own fork. Regardless, I won't commit to my own main branch after this to avoid the situation going forward.