-
Notifications
You must be signed in to change notification settings - Fork 20
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
Fix GraphCMS/Hygraph Privacy Policy and Terms of Service #1155
Conversation
b6e6aba
to
d7a12d5
Compare
What is malformed? I don't see it. I don't have a local nodejs env and don't want to install one. |
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.
Hi Kissaki, thanks for your contribution :)
The GraphCMS.json
should not be deleted, it should be empty, see the renaming a service documentation.
{
"name": "GraphCMS",
"documents": {}
}
@clementbiron if you look at the commits in this PR you can see it is not being deleted. The guidance did not exist yet when I originally created this PR; but on December 2nd I force-pushed, presumably with the adjustment to the new guidance - not deleting the file. I can see the overall diff in GitHub UI "Files Changed" still showing it as being deleted though. Maybe this is related to force-pushes also not triggering CI too? Does this repository have a configuration that prevents PR updates through force-pushes somehow? Is it a general GitHub issue? (I am used to force-pushes in GitLab updating MR commit list and overall diff - and the overall diff with a new diff version.) |
aa852ef
to
30e3e91
Compare
I tried a few force pushes, main branch merge, etc, but nothing changed what GitHub displays |
It's a GitHub Actions configuration issue. My suggested fix: OpenTermsArchive/demo-declarations#30 |
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.
Hello,
I'm sorry, I probably didn't make myself clear in my previous review.
You have renamed the GraphCMS.json
file to Hygraph.json
and this is not the right thing to do. The GraphCMS.json
file must continue to be present but it must be emptied of all terms by removing every <terms type>
entries from the documents
key in the declaration. A new Hygraph.json
file is added and completed to track the documents of the renamed service.
We should therefore have the GraphCMS.json
, GraphCMS.history.json
and Hygraph.json
files.
Regarding your problem with launching tests on the CI, we have merged a pull request based on your proposal, which we think is an acceptable compromise. Thank you very much for reporting the problem and suggesting a solution 🙏
I fixed it according to the renaming guidance. |
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.
Thank you very much! 🚀
See commit descriptions for details.
Replaces my PR #1146, Fixes #1073, #1074