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

Test that every revision builds before pushing changes?

From
Daniel Pittman <daniel@rimspace.net>
Date
Mar 26, 2009, 06:29 UTC
Message-ID
<87myb8aja1.fsf@rimspace.net>
G'day.

I would like to ensure that my commits are fully bisectable before I commit them to an upstream repository, at least to the limits of an automatic tool for testing them.

'git bisect run' is similar: it can automatically locate the breaking in a test suite, for example, but that doesn't help me in the case of three commits, A (good), B (bad) and C (good, fixing B).

I would much rather, in this case, use rebase to fix B so that it, too, builds before I push the changes and pollute a public repository with a broken changeset — and make bisect that much harder to use in future.

Regards,
        Daniel
Next: Andreas Ericsson
Message 1 of 7 in “Test that every revision builds before pushing changes?”
  1. Daniel PittmanMar 26, 2009
  2. Andreas EricssonMar 26, 2009
  3. Daniel PittmanMar 26, 2009
  4. Andreas EricssonMar 26, 2009
  5. Daniel PittmanMar 27, 2009
  6. Jeff KingMar 26, 2009
  7. Wincent ColaiutaMar 26, 2009

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.