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:
Importing a Remote Repository:
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.
Post-Cloning Steps:
After cloning, open the vault.
Install the yaos plugin in the new vault.
Path Configuration:
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!
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!