-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore: skip website tests on PRs from forks #7296
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
chore: skip website tests on PRs from forks #7296
Conversation
Thanks for the PR, @kachick! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
# The NETLIFY_TOKEN secret will not be available on PRs from forks | ||
if: (github.event_name == 'push' && github.ref_name == 'main') || (github.event.pull_request.head.repo.full_name == github.repository) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change does not block PRs in a fork to the same fork.
If we really need to skip all PRs in forks, this may be following
# The NETLIFY_TOKEN secret will not be available on PRs from forks | |
if: (github.event_name == 'push' && github.ref_name == 'main') || (github.event.pull_request.head.repo.full_name == github.repository) | |
# The NETLIFY_TOKEN secret will not be available on forks | |
if: (github.event_name == 'push' && github.ref_name == 'main') || (github.event.pull_request.head.repo.full_name == 'typescript-eslint/typescript-eslint') |
# The NETLIFY_TOKEN secret will not be available on forks | ||
if: github.repository_owner == 'typescript-eslint' | ||
# The NETLIFY_TOKEN secret will not be available on PRs from forks | ||
if: (github.event_name == 'push' && github.ref_name == 'main') || (github.event.pull_request.head.repo.full_name == github.repository) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a question, merge_group
should trigger this test? Then it may be following
if: (github.event_name == 'push' && github.ref_name == 'main') || (github.event.pull_request.head.repo.full_name == github.repository) | |
if: contains(fromJSON('["push", "merge_group"]'), github.event_name) || (github.event.pull_request.head.repo.full_name == github.repository) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't use merge queues. I don't think test triggers need to account for them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for sharing the direction! I just had confused with the trigger in here 🙇♂️
merge_group: |
cc @rubiesonthesky from #7247 with a different approach |
Thank you, #7247 seems to be aiming for a more polite way, so I close this PR. |
PR Checklist
Overview