馃悰 Fixed not ignoring nested git repositories - #105
Conversation
|
It looks like you broke a spec with this change - could you please fix it and add a spec that tests this change? Thanks. |
|
I don't really understand what the spec I broke is testing. I'd be happy to add a new spec for this change, but I've really only poked around and am not too familiar with how to test this change. |
|
I'd appreciate some help in understanding what the failing test is actually trying to test so I can fix it and get this PR merged. |
|
Test code: describe "when core.excludeVcsIgnoredPaths is set to true", ->
beforeEach ->
atom.config.set("core.excludeVcsIgnoredPaths", true)
describe "when the .gitignore matches parts of the path to the root folder", ->
beforeEach ->
ignoreFile = path.join(projectPath, '.gitignore')
fs.writeFileSync(ignoreFile, path.basename(projectPath))
it "only applies the .gitignore patterns to relative paths within the root folder", ->
dispatchCommand('toggle-file-finder')
projectView.setMaxItems(Infinity)
waitForPathsToDisplay(projectView)
runs ->
expect(projectView.list.find("li:contains(file.txt)")).toExist()What this is doing is:
|
|
This is now passing! |
|
(See also atom/git-utils#45) |
|
What can I do to help get this 馃殺? |
Adding an additional spec that tests what this fixes would help to get this shipped. |
|
I just tried to come up with a spec for this, but I'm struggling, sorry. |
f47846c to
88f87fa
Compare
88f87fa to
20cac2b
Compare
For example, suppose you have a repo, `Rainforest`, whose .gitignore is simply `*`. Inside Rainforest is another git repo, `Repo`. If you open `Repo` as your project directory, it will now be auto-completed, as the root is no longer considered ignored.
20cac2b to
088c0e7
Compare
For example, suppose you have a repo,
Rainforest,whose .gitignore is simply
*.Inside Rainforest is another git repo,
Repo.If you open
Repoas your project directory,it will now be auto-completed, as the root
is no longer considered ignored.
Fixes a situation described in #87.