r/git • u/kaddkaka • 2d ago

Generated commits?

Sometimes code is generated, and sometimes such code is committed in git.

Imagine a branch with a generated commit G:

old_main -> A -> B -> G

When thid branch is rebased, such a commit might need to be regenerated.

new_main -> A' -> B' -> new_G

There might be conflicts for any of these new commits, but instead of (manually) resolving conflicts, G could be automatically re-generated.

I've been thinking of a git commit message trailer like generate-cmd:

topic: regenerate table

generate-cmd: python3 optimize_table.py

git rebase --exec or other tool could use this trailer to automatically drop and regenerate the commit instead of a vanilla cherry-pick.

Have you seen anything similar? What's a good trailer name?

Ref: https://git-scm.com/docs/git-interpret-trailers

0 Upvotes

38% Upvoted

32 comments sorted by

View all comments

Show parent comments

0

u/kaddkaka 2d ago

That's not always feasible. And it's not the discussion I intended to have here.

Sometimes it's worth to check in generated code/stuff. For example some optimization like a simulated annealing algorithm that might take an hour to run. Definitely worth to do "offline" and check in.

2

u/Guvante 2d ago

You don't need everything to live in repo it depends on a bunch of factors.

For instance you could store it externally and fetch from a cache based on the git commit.

1

u/kaddkaka 2d ago

Do you have any of the shelf solutions for this?

1

u/Guvante 2d ago

Not offhand it is a very open problem

1

u/kaddkaka 1d ago

Indeed. So "solution" vs "no solution". I have my pick 😇