{"thread":{"id":"59155","subject":"Git submodule commits","startedAt":"2023-01-27T09:33:19Z","lastAt":"2023-01-27T09:33:19Z","messageCount":1,"participants":["Martin Terra"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"471085","messageId":"CAN_dfT+yLpM6bgUqf8MddVSj3BuY_j3eVrsyntGKj2QoHi4YQA@mail.gmail.com","threadId":"59155","inReplyTo":"CAN_dfTJY6bo7dBSBJoX7nxQMKt4VwVe2gAW7SEYM4cHffySrAQ@mail.gmail.com","subject":"Git submodule commits","fromName":"Martin Terra","fromEmail":"martin.terra@koodaripalvelut.com","sentAt":"2023-01-27T09:32:25Z","receivedAt":"2023-01-27T09:33:19Z","isPatch":false,"sender":{"key":"martin.terra@koodaripalvelut.com","avatar":null},"body":"Hi!\n\nWe have git repository A and B.\n\nA depends on B.\n\nThe team working on B has no visibility to A.\n\nHowever, team A has visibility to both A and B.\n\nYou can think of it as if repository B is outsourced.\n\nNow when team A is working on features and make a change which affects\nalso B, ideally there would be a single (single index)\ncommit/pull/etc. across A and B. Ideally, there would be no duplicate\ncopies of artifacts, i.e., optimally something from B commits only to\nB and something form A only to A (think Submodule but with ability to\ncommit also).\n\nHow can this be accomplished using Git or is it a missing/planned\nfeature in git, or is there a 3rd party tool that helps with this?\nSubmodule and subtree don't seem to have these capabilities, or do\nthey?\n\nCurrently we have these set up on cvs and committing across projects\nworks effortlessly, but cvs is in many other ways outdated.\n\nRelated topics:\n- https://jira.atlassian.com/browse/BSERV-4577\n\n\nThanks.\n\n**\nMartin\n"}]}