-
Notifications
You must be signed in to change notification settings - Fork 499
Trigger GH workflow after Drone passes #65111
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: staging
Are you sure you want to change the base?
Conversation
The GH workflow half is working on snickell/test-workflow-dispatch#2: ![]() |
The whole flow is working on code-dot-org/test-workflow-dispatch#2:
![]() |
…rg/code-dot-org into seth/drone-trigger-gh-actions
.drone.yml
Outdated
} | ||
# depends_on: | ||
# - unit | ||
# - ui |
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.
Note to self: make sure we uncomment / re-enable depends_on: ['unit', 'ui']
before merging.
🖼️ Storybook Visual Comparison Report✅ No Storybook eyes differences detected! |
….yml a chance to complete
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.
Looks good with a minor suggestion.
Co-authored-by: Stephen Liang <stephenliang@users.noreply.github.com>
Experiment to see how hard it is to trigger a GH workflow to run after Drone CI passes for a PR:
We created a "placeholder" workflow to allow us to test on this branch: #65145 . If we close this PR, we should delete the placeholder file created by that PR.