Open
Conversation
mitchdz
requested review from
1tnguyen,
bettinaheim and
bmhowe23
as code owners
Signed-off-by: Mitchell <mitch_dz@hotmail.com>
taalexander
approved these changes
Mar 10, 2026
Collaborator
taalexander
left a comment
taalexander
left a comment
There was a problem hiding this comment.
lgtm provided it works. The inter-workflow communication through artifacts is nice. Thank you!
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Signed-off-by: Mitchell <mitch_dz@hotmail.com>
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
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
3 participants
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.
Auto Publishing
This PR adds an optional auto-publishing switch to the Deployments workflow that allows the pipeline to automatically schedule a Publishing run once Deployments has completed successfully. This is especially useful when testing changes that require the Publishing workflow, so you do not have to manually monitor Deployments and trigger Publishing yourself. The option is disabled by default to preserve current behavior.
When the workflow is manually dispatched, it now creates a
publishing_requestedartifact (for example,publishing_requested) that is later consumed by the Publishing workflow to decide whether it should run for a given deployment.Example Runs
Auto-run
No auto-run