-
Notifications
You must be signed in to change notification settings - Fork 4
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
No unique resource #56
Conversation
This update has now been rebased on the revert to v.1.03. |
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.
I'm fine with the intent and the form of this change.
Github right now considers this a 9 commit-PR. I have not tried to figure out what confuses the history it sees, but I'd be confident that nothing bad will happen if you squash and merge. If, on the other hand, you insist on a merge commit, I'd first try what happens locally...
(and if you give me write privileges, I expect the merge block should be lifted, too) |
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.
This PR seems OK to me 👍
This pull request builds on the revert to v.1.03.
It must not be merged before #55 is merged, or reconsidered if it gets discarded.
It only relaxes the text for uniqueness of the RESOURCE(s) in the VOTable response