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
{{ message }}
This repository was archived by the owner on Jun 25, 2020. It is now read-only.
Currently, the scrape verb does not set a version on a repository when adding it to a workspace file, which means that workspaces created or updated from that file will use the default branch for that repository. This is a little annoying if your workspace is using tagged versions of certain repositories or if you are intentionally making a workspace that uses development branches.
It would be very useful if there was a flag that would also cause scrape to set the versions for newly-added repositories to their current version, and maybe also another option that would also change the versions for repositories that already exist in the file.
Currently, the
scrapeverb does not set a version on a repository when adding it to a workspace file, which means that workspaces created or updated from that file will use the default branch for that repository. This is a little annoying if your workspace is using tagged versions of certain repositories or if you are intentionally making a workspace that uses development branches.It would be very useful if there was a flag that would also cause
scrapeto set the versions for newly-added repositories to their current version, and maybe also another option that would also change the versions for repositories that already exist in the file.