Update CONTRIBUTING.md to educate about disable forked repo actions
ryanadhi opened this issue · 7 comments
Description
I got these constant notification from forked repo that the GitHub actions is failed, which I believe run every 30mins
Expected Behaviour
Additional Information
reproduce steps
- forked repo
- occasionally fetch new commits from original repo
- GitHub action runs and fail
is it something that expected to happen? or is there something that I did it wrong?
Thanks
TODO: Task
It's expected, since you don't provide sufficient GitHub Action secrets (a.k.a. Environment Variables) to your forked repository.
The simplest solution is by disabling GitHub Actions on your forked repository. We don't need them to be run in your forked repository since we allow Pull Requests to our upstream repository to trigger GitHub Actions in the upstream repository.
The more complex solution (which I don't think is necessary) is to provide the environment variables for your own instances, such as Netlify, Lighthouse CI, Codecov, Cypress Dashboard, etc.
To spread this information to the rest of the contributors, would you please make some changes to our CONTRIBUTING.md file to explain this situation?
Thanks!
maybe we can use this kind of solution @zainfathoni ?
maybe we can use this kind of solution @zainfathoni ?
🤔 https://github.com/arduino/arduino-cli/pull/888/files
Sounds good. Would you please update the issue description to match that approach, Mas @rubiagatra?
or yeah we need to create some documentation about disable actions https://github.community/t/stop-github-actions-running-on-a-fork/17965
We can also do this approach to educate our contributors in the meantime.
Just updated TODO task and add separate issue for github action
Just updated TODO task and add separate issue for github action
You need to add a space between the brackets like this, Mas @rubiagatra.
- [ ]
lol ups