cargo release complains about missing repo in workspaces #861
Unanswered
ManuelSopenaBallesteros
asked this question in
Q&A
Replies: 1 comment
-
cargo-release makes the assumption that a workspace is within a single repo. At least some features would require this (consolidated commits). For others to work (like updating a workspace when updating a package's version), we'd need to better understand how the workspace is being used to determine a design for that (which commit would update the workspace?). There are also a lot of corner cases with that that could make the design trickier. It would be of use to go into your underlying requirements that lead you to having this architecture so we can weigh out whether it is worth trying to support this kind of use case. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear cargo release team,
I am trying to make cargo release to work with my workspace and I am getting the following error:
I would like to ask:
Why do I need a repository for the workspace if I already have git repos for each of the workspace members? how am I supposed to manage workspaces with cargo release?
thank you very much
Beta Was this translation helpful? Give feedback.
All reactions