Skip to content

cmd/go/internal/workcmd/sync: investigate cases where sync doesn't work correctly with unreleased workspace modules #73655

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
matloob opened this issue May 10, 2025 · 0 comments

Comments

@matloob
Copy link
Contributor

matloob commented May 10, 2025

The aim of this issue is to collect cases where go work sync doesn't work correctly with workspace modules that haven't yet been released.

Two things that mentioned on #50750:

  • go work sync tried to find modules to satisfy imports that are in other workspace modules.
  • Workspace modules after a sync could have extraneous dependencies. (If there are missing requirements, they can't be "tidy", but we do run the "tidy" logic while allowing errors, and this should work as expected.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant