Extending yaos to support version control with git branch #15
Conversation
This file contains 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
…upstream flag on push, added additional pushUpstream to solve it. Add: Multibranch support. Add: Settings to import a remote vault. Add: Settings to switch between branches. Change: from yarn to npm package.
… feature note update.
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.
Hi, Mahyar
I propose introducing a multi-branch approach for Yaos. Currently, we’re using a single branch, but transitioning to multiple branches will significantly enhance the plugins ability for teams to collaborate asynchronously.
Here are the steps to achieve this:
Use the appropriate ssh or https link from GitHub to import the remote repository into an empty directory.
Specify the local directory where the repository will be cloned.
After cloning, open the vault.
Install the yaos plugin in the new vault.
Users should edit the path to match the current vault.
We can further improve this process by setting the current directory as the default for basePath.
Let’s enhance yaos for team collaboration by adopting this multi-branch strategy. Looking forward to your feedback!