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

Re: Special branch for remote

From
Phil Hord <hordp@cisco.com>
Date
Jul 27, 2011, 14:35 UTC
Message-ID
<4E302229.4030402@cisco.com>
In-Reply-To
<j0ohjr$fcd$1@dough.gmane.org>
On 07/27/2011 04:18 AM, Paulo J. Matos wrote:
Show 9 quoted lines
> Hi all,
>
> I have a huge repository for a software I am developing. In it I have
> source code, docs, experiments, tests, etc. However, I want to push
> only the src/ to the github remote, nothing else. What's the best way
> to achieve this. Do I need to simply create a new branch and then push
> the new branch to github or there's anything else involved that I need
> to know?
>

Yes, you can do this with branches. See [1] for an example of a similar workflow.

You can also manage this with submodules [2] or subtree-merge [3].

I prefer submodules since it keeps the huge stuff (docs and bins) away from my source code and makes my source code repo much more responsive.

[1] http://www.braintreepayments.com/devblog/our-git-workflow [2] http://progit.org/book/ch6-6.html [3] http://progit.org/book/ch6-7.html

HTH, Phil

Previous: Paulo J. MatosNext: Paulo J. Matos
Message 2 of 3 in “Special branch for remote”
  1. Paulo J. MatosJul 27, 2011
  2. Phil HordJul 27, 2011
  3. Paulo J. MatosJul 27, 2011

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.