add branch support for extension installation#9518
Merged
Conversation
Contributor
Author
|
@AUTOMATIC1111 would you please help to review since we plan to submit an extension allowing user to use cloud resource to accelerate train & inference process. There can be several branches, e.g. we may use 'aigc' as the stable branch for extension and 'dev' as regular development branch. |
AUTOMATIC1111
approved these changes
Apr 29, 2023
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
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.
Describe what this pull request is trying to achieve.
We are developing extension to contribute and find the 'Install from URL' tab is not support user to install from specific branch, e.g. dev, prod, we 'd like to add a 'branch name' option to allow user switch from difference branches of the same repo, especially for the extension in development phase with different feature set provided per branch. Existing user experience will remain and new option can be empty.
Additional notes and description of your changes
More technical discussion about your changes go here, plus anything that a maintainer might have to specifically take a look at, or be wary of.
Environment this was tested in
List the environment you have developed / tested this on. As per the contributing page, changes should be able to work on Windows out of the box.
Screenshots or videos of your changes
If applicable, screenshots or a video showing off your changes. If it edits an existing UI, it should ideally contain a comparison of what used to be there, before your changes were made.
This is required for anything that touches the user interface.