IssueRaiser

Then you get the annoying problem of having to push an update to that repo and wait for the new version before you can merge changes into...

Then you get the annoying problem of having to push an update to that repo and wait for the new version before you can merge changes into the new repo which use the new version. It’s tightly coupled, so they should be co-located.

Posted by klysm on Jun 16, 2022, 11:14 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments

hackernews (Other)

Then you get the annoying problem of having to push an update to that repo and wait for the new version before you can merge changes into...

klysmJun 16, 2022, 11:14 AM

Then you get the annoying problem of having to push an update to that repo and wait for the new version before you can merge changes into the new repo which use the new version. It’s tightly coupled, so they should be co-located.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue