From: "Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Elijah Newren <newren@gmail.com>
Subject: [PATCH 0/2] merge-tree: add new --mergeability-only option
Date: Sat, 10 May 2025 22:02:39 +0000 [thread overview]
Message-ID: <pull.1920.git.1746914561.gitgitgadget@gmail.com> (raw)
This adds a new flag, --mergeability-only, to git merge-tree, which
suppresses all output and leaves only the exit status (reflecting successful
merge or conflict). This is useful for Git Forges in cases where they are
only interested in whether two branches can be merged, without needing the
actual merge result or conflict details.
The advantage of the flag is two fold:
* The merge machinery can exit once it detects the first conflict, instead
of continuing to compute merge result information
* The merge machinery can avoid writing merged blobs and trees to the
object store when in the outer layer of the merging process (more details
in the first commit message).
Elijah Newren (2):
merge-ort: add a new mergeability_only option
merge-tree: add a new --mergeability-only flag
Documentation/git-merge-tree.adoc | 6 +++++
builtin/merge-tree.c | 22 ++++++++++++++++++
merge-ort.c | 38 +++++++++++++++++++++++++------
merge-ort.h | 1 +
t/t4301-merge-tree-write-tree.sh | 38 +++++++++++++++++++++++++++++++
5 files changed, 98 insertions(+), 7 deletions(-)
base-commit: 6c0bd1fc70efaf053abe4e57c976afdc72d15377
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1920%2Fnewren%2Fmergeability-only-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1920/newren/mergeability-only-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1920
--
gitgitgadget
next reply other threads:[~2025-05-10 22:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-10 22:02 Elijah Newren via GitGitGadget [this message]
2025-05-10 22:02 ` [PATCH 1/2] merge-ort: add a new mergeability_only option Elijah Newren via GitGitGadget
2025-05-10 22:02 ` [PATCH 2/2] merge-tree: add a new --mergeability-only flag Elijah Newren via GitGitGadget
2025-05-12 17:04 ` [PATCH 0/2] merge-tree: add new --mergeability-only option Junio C Hamano
2025-05-12 17:41 ` Elijah Newren
2025-05-12 18:27 ` Junio C Hamano
2025-05-12 18:37 ` Elijah Newren
2025-05-12 23:42 ` [PATCH v2 0/2] merge-tree: add new --dry-run option Elijah Newren via GitGitGadget
2025-05-12 23:42 ` [PATCH v2 1/2] merge-ort: add a new mergeability_only option Elijah Newren via GitGitGadget
2025-05-12 23:42 ` [PATCH v2 2/2] merge-tree: add a new --dry-run flag Elijah Newren via GitGitGadget
2025-05-13 7:15 ` Kristoffer Haugsbakk
2025-05-13 15:28 ` Elijah Newren
2025-05-13 13:24 ` Junio C Hamano
2025-05-13 15:30 ` Elijah Newren
2025-05-14 14:08 ` Junio C Hamano
2025-05-14 0:24 ` [PATCH v3 0/2] merge-tree: add new --dry-run option Elijah Newren via GitGitGadget
2025-05-14 0:24 ` [PATCH v3 1/2] merge-ort: add a new mergeability_only option Elijah Newren via GitGitGadget
2025-05-14 0:24 ` [PATCH v3 2/2] merge-tree: add a new --dry-run flag Elijah Newren via GitGitGadget
2025-05-15 13:07 ` Junio C Hamano
2025-05-16 13:18 ` Phillip Wood
2025-05-16 16:03 ` Elijah Newren
2025-05-14 15:34 ` [PATCH v3 0/2] merge-tree: add new --dry-run option Kristoffer Haugsbakk
2025-05-16 20:04 ` [PATCH v4 0/2] merge-tree: add new --quiet option Elijah Newren via GitGitGadget
2025-05-16 20:04 ` [PATCH v4 1/2] merge-ort: add a new mergeability_only option Elijah Newren via GitGitGadget
2025-05-16 20:04 ` [PATCH v4 2/2] merge-tree: add a new --quiet flag Elijah Newren via GitGitGadget
2025-05-17 19:52 ` Kristoffer Haugsbakk
2025-05-17 19:57 ` Kristoffer Haugsbakk
2025-05-19 9:05 ` [PATCH v4 0/2] merge-tree: add new --quiet option Phillip Wood
2025-05-19 15:59 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.1920.git.1746914561.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).