-
-
Notifications
You must be signed in to change notification settings - Fork 32.6k
[test] Trigger CircleCI tests from PRs #36026
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
base: v5.x
Are you sure you want to change the base?
Conversation
|
1259d1f
to
5365ca9
Compare
name: Bundling tests | ||
|
||
on: pull_request | ||
|
||
permissions: read-all | ||
|
||
jobs: | ||
trigger-circleci: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- name: Start CircleCI bundling tests | ||
uses: CircleCI-Public/[email protected] | ||
env: | ||
CCI_TOKEN: ${{ secrets.CIRCLECI_TOKEN }} | ||
with: | ||
GHA_Meta: 'workflow:bundling' |
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.
What's the purpose of this GitHub action?
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 was trying out different things. I was working on an action that would trigger a CircleCI build only on some branches (release/*
, not enabled here right now). But I learned this isn't possible as there's no access to secrets when running actions triggered from PRs. I'll look for another approach.
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.
It might be possible to configure it with CircleCI yaml.
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.
AFAIK CircleCI doesn't know the original branch name the PR is coming from
No description provided.