-
Notifications
You must be signed in to change notification settings - Fork 238
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
Setup CI to avoid committing locally built files #114
Comments
It seems less obvious to do than I thought. Here are some interesting content:
I'm investigating how to do that, but since I'm a beginner with travis CI, any help is welcomed. |
There is also a workflow using GitHub Actions: https://docs.github.com/en/actions/language-and-framework-guides/using-nodejs-with-github-actions |
OK, to answer you question, @walmik, after a few research, I couldn't find any documentation showing a CI tool commiting back to the repo. It makes sense from a security standpoint: having an external worker able to write to the codebase, using a token, seems a bit extreme. It seems that there is a widely shared philosophy of "the codebase is for humans only". The machines need to use other services, with read-only rights on the codebase. IMHO the easiest workflow is:
If we chose to do this, I guess we have to:
|
Originally posted by @walmik in #111 (comment)
The text was updated successfully, but these errors were encountered: