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

Only track built files for final output?

From
Leam Hall <leamhall@gmail.com>
Date
Aug 20, 2019, 12:21 UTC
Message-ID
<477295c5-f817-e32b-04fd-a41ddfbbac0a@gmail.com>
Hey all, a newbie could use some help.

We have some code that generates data files, and as a part of our build process those files are rebuilt to ensure things work. This causes an issue with branches and merging, as the data files change slightly and dealing with half a dozen merge conflicts, for files that are in an interim state, is frustrating. The catch is that when the code goes to the production state, those files must be in place and current.

We use a release branch, and then fork off that for each issue. Testing, and file creation, is a part of the pre-merge process. This is what causes the merge conflicts.

Right now my thought is to put the "final" versions of the files in some other directory, and put the interim file storage directory in .gitignore. Is there a better way to do this?

Thanks!
Leam
Next: Pratyush Yadav
Message 1 of 6 in “Only track built files for final output?”
  1. Leam HallAug 20, 2019
  2. Pratyush YadavAug 20, 2019
  3. Leam HallAug 20, 2019
  4. Pratyush YadavAug 20, 2019
  5. Phil HordAug 20, 2019
  6. Randall S. BeckerAug 20, 2019

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.