Skip to content
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

Play 3.0.4 + Play JSON 3.0.4 #27233

Closed
wants to merge 2 commits into from
Closed

Play 3.0.4 + Play JSON 3.0.4 #27233

wants to merge 2 commits into from

Conversation

mkurz
Copy link
Contributor

@mkurz mkurz commented Jun 18, 2024

@mkurz mkurz requested a review from a team as a code owner June 18, 2024 21:14
@ioannakok ioannakok added this to the Health milestone Jun 24, 2024
@ioannakok
Copy link
Contributor

Thanks @mkurz! Trying to find a solution of how we can accept your PRs without re-raising but for now I re-raised this one here: #27294.

@mxdvl
Copy link
Contributor

mxdvl commented Jul 9, 2024

Sorry for the annoying workflow and thanks for raising @mkurz 🙇

@mxdvl mxdvl closed this Jul 9, 2024
@mkurz mkurz deleted the play304 branch July 9, 2024 14:27
@mkurz
Copy link
Contributor Author

mkurz commented Jul 9, 2024

For me I don't mind your workflow. I open these PRs just to let you know about new Play releases.

rtyley added a commit that referenced this pull request Jul 25, 2024
As mentioned in github/docs#6861:

> It is common for projects to include a secret for deploying things and an action that uses that secret.
>
> When one forks that repository, the secret won't be present and the workflow will break.
>
> This experience is incredibly painful.

For guardian/frontend, we're using [actions-riff-raff](https://github.com/guardian/actions-riff-raff), which needs a `roleArn` which is provided as a repository secret. For PRs like #27233, from an external contributor, the CI appears to fail, even though all tests have passed.

### CI never runs on forks unless we authorise the contributor

The [GitHub docs](https://docs.github.com/en/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks#approving-workflow-runs-on-a-pull-request-from-a-public-fork) say:

> By default, all first-time contributors require approval to run workflows.

...so it could be argued that ideally, the build should still produce the riff-raff artifact for fork PRs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants