build(ci): trigger CI workflow on dependabot merge [DX-665] #2205
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Add
workflow_dispatchtrigger to main CI workflow and configure dependabot workflow to explicitly trigger CI after auto-merge.Description
workflow_dispatchtomain.yamlto allow manual workflow triggeringdependabot-approve-and-request-merge.yamlto retrieve Vault secrets and trigger CI workflow after mergeMotivation and Context
When dependabot PRs are auto-merged, the workflow token used doesn't trigger push-based workflows by design. This change explicitly triggers the CI workflow after merge.
PR Checklist
CONTRIBUTING.mdfile