-
Notifications
You must be signed in to change notification settings - Fork 831
Remove accidentally-exported internal macros #1177
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
Remove accidentally-exported internal macros #1177
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK c9f2aae0c35a684e51f9273333c25f1b13d1d4ee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK c9f2aae0c35a684e51f9273333c25f1b13d1d4ee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK c9f2aae0c35a684e51f9273333c25f1b13d1d4ee
I think rebase would fix this after we merged #1175 . But I don't mind merging it as this should pass on merge commit |
Hmm, I thought GitHub would test against current master, not against one that was there at the time of opening. |
94eeabf
c9f2aae
to
94eeabf
Compare
No it does not. One of the main reasons that we have the merge script that runs tests on the merge commit. It is also possible to PR with green lights passes checks from its own CI config, but fails master. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reACK 94eeabf
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 94eeabf
Closes #1176