• Pyro@programming.dev
    107·
    13 hours ago

    “Changes” encompass more than you think. Creating / Deleting files are also changes, not just edits to a file.

    • If the change is an edit to a tracked file, “Discard Changes” will reverse the edit.
    • If the change is deleting a tracked file, “Discard Changes” will restore it back.
    • If the change is a new untracked file, “Discard Changes” will remove it as intended.

    It can also be all of them at the same time, which is why VSCode uses “Changes” instead of “Files”.

    • candybrie@lemmy.world
      7·
      9 hours ago

      If the change is a new untracked file

      Wasn’t the issue that it deleted a bunch of preexisting untracked files? So old untracked files.

      • Eranziel@lemmy.world
        33·
        10 hours ago

        I find it difficult to lay the blame with VSCode when the terminology belongs to git, which (even 7 years ago) was an industry standard technology.

        People using tools they don’t understand and plowing ahead through scary warnings will always encounter problems.