sublimehq / sublime_merge

Issue tracker for Sublime Merge
https://www.sublimemerge.com
276 stars 14 forks source link

gitignore not interpreted correctly #1147

Open gukohl opened 3 years ago

gukohl commented 3 years ago

Version info

Description

When editing files through Sublime Merge (e.g. Resolve conflicts - accept ours) then gitignore can get misinterpreted and changed file disappears from list of changed files.

Steps to reproduce

Steps to reproduce the behavior:

  1. Open a repository that does have changes that are committed locally.
  2. Pull from remote origin with a changed file in a way that a conflict gets created. Precondition: this file resides in a folder let's say /js/folder/, and a gitignore file in the root states to exclude: folder/
  3. For the file select Resolve conflicts, and select to accept the changes.

Actual behavior

Expected behavior

The file gets updated and remains in the list of changed files. No message showing in Sublime Merge telling like "a changed file gets disregarded since in it is excluded by one of the gitignore rules".

stinos commented 3 years ago

git status does not list the changed file

If the actual git command git status does not list the file, arguably SM shouldn't either because it normally does what git does

gukohl commented 3 years ago

"normally"

Look into my description, git actually does work as intended. The problem occurs for me only when using SM's Resolve conflicts action.

On 17. May 2021 at 12.39.40, stinos @.***> wrote:

git status does not list the changed file

If the actual git command git status does not list the file, arguably SM shouldn't either because it normally does what git does

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/sublimehq/sublime_merge/issues/1147#issuecomment-842179167, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGI2WRXIFSKRAOWAUBMCR7TTODP5ZANCNFSM45ACUNDQ .