From: "ctmbl via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: ClementMabileau <mabileau.clement@gmail.com>,
ctmbl <mabileau.clement@gmail.com>
Subject: [PATCH 1/2] branch: improve error log on branch not found by checking remotes refs
Date: Wed, 22 Mar 2023 09:42:05 +0000 [thread overview]
Message-ID: <91cb506968a11fbceba856a40b14bed0c4e647bc.1679478126.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1476.git.git.1679478126.gitgitgadget@gmail.com>
From: ctmbl <mabileau.clement@gmail.com>
when failing to delete a branch with `git branch -d <branch>` because
of branch not found, try to find a remote refs matching `<branch>`
and if so add an hint:
`Did you forget --remote?` to the error message
Signed-off-by: Clement Mabileau <mabileau.clement@gmail.com>
---
builtin/branch.c | 28 +++++++++++++++++++++++-----
1 file changed, 23 insertions(+), 5 deletions(-)
diff --git a/builtin/branch.c b/builtin/branch.c
index f63fd45edb9..8e768761b9b 100644
--- a/builtin/branch.c
+++ b/builtin/branch.c
@@ -216,10 +216,12 @@ static int delete_branches(int argc, const char **argv, int force, int kinds,
struct string_list refs_to_delete = STRING_LIST_INIT_DUP;
struct string_list_item *item;
int branch_name_pos;
+ char* FMT_REMOTES = "refs/remotes/%s";
+ char* FMT_BRANCHES = "refs/heads/%s";
switch (kinds) {
case FILTER_REFS_REMOTES:
- fmt = "refs/remotes/%s";
+ fmt = FMT_REMOTES;
/* For subsequent UI messages */
remote_branch = 1;
allowed_interpret = INTERPRET_BRANCH_REMOTE;
@@ -227,7 +229,7 @@ static int delete_branches(int argc, const char **argv, int force, int kinds,
force = 1;
break;
case FILTER_REFS_BRANCHES:
- fmt = "refs/heads/%s";
+ fmt = FMT_BRANCHES;
allowed_interpret = INTERPRET_BRANCH_LOCAL;
break;
default:
@@ -263,9 +265,25 @@ static int delete_branches(int argc, const char **argv, int force, int kinds,
| RESOLVE_REF_ALLOW_BAD_NAME,
&oid, &flags);
if (!target) {
- error(remote_branch
- ? _("remote-tracking branch '%s' not found.")
- : _("branch '%s' not found."), bname.buf);
+ char* MISSING_REMOTE_REF_ERROR_MSG = "remote-tracking branch '%s' not found.";
+ char* MISSING_BRANCH_ERROR_MSG = "branch '%s' not found.";
+ char* MISSING_BRANCH_HINT_MSG = "branch '%s' not found.\n"
+ "Did you forget --remote?";
+
+ if (remote_branch) {
+ error(_(MISSING_REMOTE_REF_ERROR_MSG), bname.buf);
+ } else {
+ char* virtual_name = mkpathdup(FMT_REMOTES, bname.buf);
+ char* virtual_target = resolve_refdup(virtual_name,
+ RESOLVE_REF_READING
+ | RESOLVE_REF_NO_RECURSE
+ | RESOLVE_REF_ALLOW_BAD_NAME,
+ &oid, &flags);
+ if (virtual_target)
+ error(_(MISSING_BRANCH_HINT_MSG), bname.buf);
+ else
+ error(_(MISSING_BRANCH_ERROR_MSG), bname.buf);
+ }
ret = 1;
continue;
}
--
gitgitgadget
next prev parent reply other threads:[~2023-03-22 9:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 9:42 [PATCH 0/2] branch: improve error log on branch not found by checking remotes refs ClementMabileau via GitGitGadget
2023-03-22 9:42 ` ctmbl via GitGitGadget [this message]
2023-03-22 9:42 ` [PATCH 2/2] Fix mem leak in branch.c due to not-free newly added virtual_name variable ctmbl via GitGitGadget
2023-03-22 16:52 ` Junio C Hamano
2023-03-22 20:00 ` Clement Mabileau
2023-03-22 20:52 ` Junio C Hamano
2023-03-22 20:03 ` [PATCH v2] branch: improve error log on branch not found by checking remotes refs ClementMabileau via GitGitGadget
2023-03-22 22:25 ` Junio C Hamano
2023-03-23 15:51 ` Clement Mabileau
2023-04-04 13:30 ` Clement Mabileau
2023-04-04 16:24 ` Junio C Hamano
2023-04-05 9:15 ` Clement Mabileau
2023-04-05 11:43 ` [PATCH v3] " ClementMabileau via GitGitGadget
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=91cb506968a11fbceba856a40b14bed0c4e647bc.1679478126.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=mabileau.clement@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).