-
-
Notifications
You must be signed in to change notification settings - Fork 199
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
Rename pmf and X #1164
Rename pmf and X #1164
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1164 +/- ##
=======================================
Coverage 73.33% 73.33%
=======================================
Files 72 72
Lines 11387 11387
=======================================
Hits 8351 8351
Misses 3036 3036
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
I like it. Changelog update? |
PR econ-ark/DemARK#187 fixes DemARK's after this PR is merged. |
Do we have a way to check whether any REMARKs might be broken? In principle, REMARKs should all have version control on them so should not break. In practice, I doubt that they all do (or do so correctly). |
To broaden my prior point, if I'm not mistaken, at the moment our procedure is to run DemARK checks nightly by running against the master branch of the development HARK repo. Would it be easy to set things up so that the DemARKs are also tested against any new PR's? Or, at least, could we somehow automatically remind the poster of a new PR to check DemARKs (and maybe REMARKs)? |
See #1051, #1159