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
ShinyDeploy should consist of submodules to the original repos in which we are developing apps. Each submodule could link, e.g., to a deploy branch, so that development could still happen in master.
Here's an example:
Legend and ShinyDeploy link via submodule to LegendBasicViewer. The Legend link is for all branches and the ShinyDeploy link is for the deploy branch.
Other ideas?
The text was updated successfully, but these errors were encountered:
In general I think this is a good idea, but I'm a bit vague on the details. Are you saying the LegendBasicViewer folder in the ShinyDeploy repo master branch would be linked to the LegendBasicViewer folder in the Legend repo deploy branch, such that any updates on the Legend repo side would automatically appear in the ShinyDeploy repo?
A related question: what happened to the submodule link for SkeletonCompartiveEffectStudy? The copy in StudyProtocolSandbox no longer is up to date with the SkeletonCompartiveEffectStudy repo.
Here is an idea:
ShinyDeploy
should consist of submodules to the original repos in which we are developing apps. Each submodule could link, e.g., to adeploy
branch, so that development could still happen inmaster
.Here's an example:
Legend
andShinyDeploy
link via submodule toLegendBasicViewer
. TheLegend
link is for all branches and theShinyDeploy
link is for thedeploy
branch.Other ideas?
The text was updated successfully, but these errors were encountered: