git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Git submodule commits

From
MTMartin Terra <martin.terra@koodaripalvelut.com>
Date
Jan 27, 2023, 09:32 UTC
Message-ID
<CAN_dfT+yLpM6bgUqf8MddVSj3BuY_j3eVrsyntGKj2QoHi4YQA@mail.gmail.com>
In-Reply-To
<CAN_dfTJY6bo7dBSBJoX7nxQMKt4VwVe2gAW7SEYM4cHffySrAQ@mail.gmail.com>
Hi!
We have git repository A and B.
A depends on B.
The team working on B has no visibility to A.
However, team A has visibility to both A and B.
You can think of it as if repository B is outsourced.

Now when team A is working on features and make a change which affects also B, ideally there would be a single (single index) commit/pull/etc. across A and B. Ideally, there would be no duplicate copies of artifacts, i.e., optimally something from B commits only to B and something form A only to A (think Submodule but with ability to commit also).

How can this be accomplished using Git or is it a missing/planned feature in git, or is there a 3rd party tool that helps with this? Submodule and subtree don't seem to have these capabilities, or do they?

Currently we have these set up on cvs and committing across projects works effortlessly, but cvs is in many other ways outdated.

Related topics:
- https://jira.atlassian.com/browse/BSERV-4577
Thanks.

** Martin

Message 1 of 1 in “Git submodule commits”
  1. Martin TerraJan 27, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.