Enable deployments for experimental branches #880
Merged
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
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
amccaskey
approved these changes
Nov 8, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 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.
This PR enables deployments from experimental/* branches in much the same way as we do for releases/* branches;
The docker images built during deployment will be pushed to the nightly channel on NGC, and python wheels can be downloaded as artifact. The only exception is that we do not publish docs by default for these branches. However, they can be published manually by running the documentation workflow - please enter the name of the feature as "version" argument in that case, and link it in the README that is included in the container. When creating the initial push to an experimental/* branch, make sure to first update the README in docker/release to describe the feature, and how to use it - update this README as necessary when you update the branch.
I've enabled branch protection rules for experimental branches, and made the necessary changes in environment definitions.