-
Notifications
You must be signed in to change notification settings - Fork 18
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
ECTO release 3-10-2020 #90
Conversation
@matentzn looks like we have some conflicts with the PR, not certain what they mean |
This happens when you are working on a branch that is outdated compared to master. These are the steps:
Very important: This is only safe in this case because I know that these are files that are automatically generated (the ofn files are the OWL versions of your patterns, and definitions.owl is the merged ontology of all your ofn files). This is not generally true, especially not if there are files involved that you have actually edited, like ecto-edit.owl or any of tsv are in conflict. After they are deleted, you need to make sure your release branch is up-to-date with master: https://stackoverflow.com/questions/3876977/update-git-branches-from-master Lastly, you run your release again, and push it to your release branch. The conflicts will have disappeared. In a future scenario, where important files are in conflict, contact me again and I will walk you through the proper |
deletion to resolve conflicts
deletion to resolve conflicts
deletion to resolve conflicts
deletion to resolve conflicts
deletion to resolve conflicts
@matentzn are we good to merge the PR now? |
Dont merge yet; I will take care of it. Great work! |
Erroneous whitespace in exposure to environmental material pattern
Made sure that disjoint hack works for test (merging ontology first)
- Changed license property, added description (to be OBO conformant). - removed the `exposure event or process` class from the edit file as this is already in RO and coming from there.
Updates to patterns for release