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

Allow e2e workflow to run correctly on forked repos #1775

Open
spwoodcock opened this issue Sep 10, 2024 · 0 comments
Open

Allow e2e workflow to run correctly on forked repos #1775

spwoodcock opened this issue Sep 10, 2024 · 0 comments
Labels
devops Related to deployment or configuration effort:low Likely a few hours good first issue Good for newcomers help wanted Extra attention is needed priority:low Backlog of tasks that will be addressed in time

Comments

@spwoodcock
Copy link
Member

spwoodcock commented Sep 10, 2024

Describe the bug

  • The e2e github workflow runs fine on deploy, and on PRs from those with repo access.
  • The workflow consistently fails on PRs from forked repos.
  • This suggests a permission issue and needs to be investigated.

To Reproduce

Check workflows running in PRs from @NSUWAL123

He uses a forked repo in the team, specifically for identifying these sorts of issues 👍

Expected behavior

  • The workflow runs and tests complete.
  • This is an interesting issue as it's causing timeouts in playwright, not permission issues as far as I can tell.
  • Perhaps a good place to start debugging is the github environment used? Maybe a forked repo doesn't have permission to use the vars there, causing the URLs to be wrong and a timeout?
@spwoodcock spwoodcock added devops Related to deployment or configuration effort:low Likely a few hours good first issue Good for newcomers help wanted Extra attention is needed priority:low Backlog of tasks that will be addressed in time labels Sep 10, 2024
@spwoodcock spwoodcock added this to the Update production devops milestone Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops Related to deployment or configuration effort:low Likely a few hours good first issue Good for newcomers help wanted Extra attention is needed priority:low Backlog of tasks that will be addressed in time
Projects
Development

No branches or pull requests

1 participant