Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

\ExcludedTfvcFoldersForIndexing.ps1 folder format

Open
#82 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
42/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
powershell
Domain
documentation

Research direction

Start with ExcludedTfvcFoldersForIndexing.ps1 and the existing Read-Host documentation that says "Specify comma separated list of folders to Exclude from Indexing." Confirm the valid TFVC folder syntax and whether exclusions apply recursively or only to the named folder, then update that documentation to state the answers clearly.

Written by the indexing model from the issue text.

Description

The documentation does not specify how to format TFVC folder paths.

Which one of these is it?

  • $/Project/Folder1,$/Project/Folder2
  • /Folder1,/Folder2
  • Folder1,Folder2

I can do a PR on the existing Read-Host doc (which is currently "Specify comma separated list of folders to Exclude from Indexing") to clarify this once I know what is the correct format.

Additionally, I'm assuming this exclusion works recursively on all sub folders. What if I want to exclude only that folder?

Dominant language
PowerShell
Stars
57
Forks
68
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from microsoft/Code-Search

All issues in microsoft/Code-Search

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.