You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Managing multiple branches or tags seems necessary for plugin-developers to handle future breaking changes. Introducing changes that alter configuration or behavior would cause issues for existing users. So i would like to eg. have a stable "version1". Then at some point i could start a "version2" where i introduce breaking changes, while still giving existing users access to "version1" and security patches for version1.
I explored if i could add a tag or branch to a git URL, but that doesnt seem to be possible.
I suggest implementing git checkout, so you can do:
I thought about adding it as .require(url,revision), but that would probably not be optimal if people just want to switch branch, whilst already having the repo installed.
Using git checkout provides access to checking out tags, branching and even reverting to a previous commit using its hash, enabling retrieval of older versions when needed.
The text was updated successfully, but these errors were encountered:
Managing multiple branches or tags seems necessary for plugin-developers to handle future breaking changes. Introducing changes that alter configuration or behavior would cause issues for existing users. So i would like to eg. have a stable "version1". Then at some point i could start a "version2" where i introduce breaking changes, while still giving existing users access to "version1" and security patches for version1.
I explored if i could add a tag or branch to a git URL, but that doesnt seem to be possible.
I suggest implementing git checkout, so you can do:
I thought about adding it as
.require(url,revision)
, but that would probably not be optimal if people just want to switch branch, whilst already having the repo installed.Using git checkout provides access to checking out tags, branching and even reverting to a previous commit using its hash, enabling retrieval of older versions when needed.
The text was updated successfully, but these errors were encountered: