-
Notifications
You must be signed in to change notification settings - Fork 29
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
Generate the release diff with the OAK output #3377
Conversation
Fixes issues with reaching the limit number of characters in the release notes
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.
No objection to the generation of another diff with OAK, but since we already have a src/ontology/diffs
directory with a small Makefile
to generate the existing diffs, I’d rather have the new rule added to that Makefile than directly to the uberon.Makefile
. Especially since src/ontology/diffs/Makefile
already contains a rule to download the latest released OBO version of the ontology, so there’s no need to duplicate that in uberon.Makefile
.
This PR has not seen any activity in the past month; if nobody comments or reviews it in the next week, the PR creator will be allowed to proceed with merging without explicit approval, should they wish to do so. |
Move the rule that produces the $(REPORTSDIR)/diff_release_oak.md diff file to the dedicated diffs/Makefile, and add it to the `all` target of that Makefile so that the new diff is automatically generated as part of the `release-diff` target.
Thank you @gouttegd! |
Fixes issues with reaching the limit number of characters in the release notes.