GitHub Community
-
|
I create a media site linked to an external CMS. The media site is built with the Jamstack architecture, and GitHub Actions is used to build and deploy the pages of the Jamstack site. In this architecture, after updating CMS articles, the page needs to be built and deployed to deliver the latest articles. This can be achieved by using the Scheduled Action of GitHub Actions and executing the build workflow periodically (e.g every 0 am). However, using GitHub Actions only for updating articles without changing the site code (HTML, CSS, JS, etc.) seems to be a serverless computing use beyond the scope of CI/CD. This seems to violate the GitHub Actions Terms of Service (https://docs.github.com/en/github/site-policy/github-additional-product-terms#4-pages). Is using GitHub Actions for article updates a problem with terms of use? |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments
-
|
Hi @nyamadori, Glad to see you in Github Community Forum! No, the terms of use referred is talking about the Github pages, which is not related to your artical site update. Github actions mostly act the same as your local machine. Hence, firstly please try to figure out how to use command on local machine to update an article on a Jamstack site, and then you can transfer the code to github workflow. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your reply! Correctly: I’m afraid that I’m not violating the following text in the above terms and conditions:
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @nyamadori, Thanks for your reply! Yes, please don’t use github actions for serverless computing according to the product terms. |
Beta Was this translation helpful? Give feedback.
-
|
I’ll ask a question to clear up my understanding. Is “serverless computing” a process that does not reference the Git repository or the code in the repository? |
Beta Was this translation helpful? Give feedback.
-
|
I think that @nyamadori’s question and concerns are a good point, the Terms of Use document seems to be vague regarding what constitutes “serverless computing” (a term which, in itself, could be subject of multiple interpretations), and (IMO) adding to the document a few practical examples of violating uses (and possibly of legitimate ones) could help clarify the difference. |
Beta Was this translation helpful? Give feedback.
-
|
After thinking about this post for a few days, I thought it would be better to post a ticket to GitHub Support for the terms of service instead of asking it on GitHub Community. I’m concerned about creating confusion in discussions on the GitHub Community, for example, with non-employees giving inappropriate answers to the Terms of Service. So I’m going to post a ticket to GitHub Support with this post. |
Beta Was this translation helpful? Give feedback.
-
|
nyamadori:
Please, do share a summary of the reply on this post when you get a reply, or even ask explicit permission to paste the email reply here. I personally think that your question is a good topic for this forum since it concerns the whole community, but I do understand your concerns about the possibility of adding confusion through unofficial replies (although the GH logo on admins’ avatar icons clarifies whose replies are official). |
Beta Was this translation helpful? Give feedback.
-
|
Yes, This is my question also. |
Beta Was this translation helpful? Give feedback.
-
|
nyamadori:
The GitHub Terms for Additional Products and Features has been updated/revised since, and it doesn’t seem to contain the above quoted clause anymore — clearer definitions of what may or may not be done using Actions are now provided. |
Beta Was this translation helpful? Give feedback.
The GitHub Terms for Additional Products and Features has been updated/revised since, and it doesn’t seem to contain the above quoted clause anymore — clearer definitions of what may or may not be done using Actions are now provided.