Skip to content

Commit

Permalink
add github actions doc on pull-request events trigger
Browse files Browse the repository at this point in the history
  • Loading branch information
juliamrch committed Dec 26, 2023
1 parent c0577fe commit d0ebf2e
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,9 @@ Place this script in your repository in `.github/workflows/` and modify the foll
- `CLEVER_SECRET` and `CLEVER_TOKEN`: find them in your `clever-tools.json` after installing the CLI (example path on Mac: `~/.config/clever-cloud/clever-tools.json`)
- `ORGA_ID`: the organisation in which your app is created

⚠️ This script runs in the context of the base repository and won't work accross forks, because your fork won't have access to secrets from this repository. This is a GitHub Action security measure and there isn't any way of overriding this using GitHub Actions. Any pull request from a fork will therefore fail, consider warning your contributors about this.
⚠️ This script runs in the context of the base repository and won't work accross forks, because the branch from your fork won't exist in this one. It uses `pull_request_target` as a trigger event to access secrets needed to deploy.

Generally speaking, forks won't have access to secrets [from any base repository](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflows-in-forked-repositories-1). This is a GitHub Action security measure and there isn't any way of overriding this using GitHub Actions. **Any pull request from a fork will therefore fail**, consider warning your contributors about this.

## Inject App Secrets

Expand Down

0 comments on commit d0ebf2e

Please sign in to comment.