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

Deleting a branch after merging it results in "there may be uncommitted changes"

From
JLJoshua Lamusga <joshlamusga@gmail.com>
Date
Oct 5, 2017, 03:04 UTC
Message-ID
<CA+bN42rdGATo-T-ibWRMvXsKJwgX6Lp_xSM+MEQdc3tOejshog@mail.gmail.com>

Hello, I'm trying to understand Git and the mess I've made. Some time ago, I did crazy things like adding to master even though I was working in develop, leaving it a commit ahead and X commits behind. I did crazier things, like trying to amend a previous post's message.

Anyway, I follow a very simple merging model for this one-person project. Recently, I made a new local branch off of develop called feature-printing. After checking out feature-printing, making my changes, and committing changes, I merged it with develop. I then immediately tried to delete feature-printing, which resulted in a prompt asking if I was sure since it might contain uncommitted changes. Though I've seen this problem many times on the internet, I haven't seen it in the context of literally just merging. There are 0 steps between merging and deleting the old branch.

All of this is done in Visual Studio's GUI for Git. Any ideas?
Next: Florian Weimer
Message 1 of 2 in “Deleting a branch after merging it results in "there may be uncommitted changes"”
  1. Joshua LamusgaOct 5, 2017
  2. Florian WeimerOct 17, 2017

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.