libgit2 / libgit2/libgit2sharp

should ignore BOM in .gitignore

Open
#1,903 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
3.5k
Forks
925
PR merge metrics
No merged PRs in 30d

Description

You are opening a bug report against the LibGit2Sharp project: we
use GitHub Issues for tracking bug reports and feature requests. If
you have a question about an API or usage, please ask on StackOverflow:
http://stackoverflow.com/questions/tagged/libgit2sharp.

Otherwise, to report a bug, please fill out the reproduction steps
(below) and delete these introductory paragraphs. Thanks!

Reproduction steps
  1. Try this with an existing repo. Put a BOM at the header of a .gitignore file, and a directory to ignore such as .vs/ on the same (top, first) line of the .gitignore file.
  2. confirm command-line native git still ignores the .vs directory.
  3. Write a quick program that uses libgit2sharp to look at the above repo and get the status.
  4. Get the status and note the status is marked dirty, and the .vs dir is listed as untracked, not ignored.
Expected behavior

The status reported by libgit2sharp should report status is clean. It should ignore the .vs dir.

Actual behavior

The .vs dir is listed as untracked, not ignored.

The status is dirty.

Version of LibGit2Sharp (release number or SHA1)

0.26.2

Operating system(s) tested; .NET runtime tested

Windows 10

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the report with LibGit2Sharp 0.26.2 on Windows 10 using a .gitignore whose first line begins with a BOM and names .vs/. Compare its status with native Git. Done means LibGit2Sharp reports a clean status and marks .vs as ignored rather than untracked.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, git
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.