GitHub PR File Filter
Overview
Hide tests and selected file types in GitHub PR file trees and diffs, with configurable presets, patterns, and exceptions.
Hide test files in the tree and diff view of GitHub pull requests. Open the menu beside "Filter files" and enable "Hide test files". Settings let you choose naming presets, hide extensions or path patterns, and add exceptions. Preview a path before saving. Rules can apply to either panel or both, and can be imported or exported as JSON. Turn off "Enable file filtering" to restore entries hidden by the extension. Existing platform filters still apply. Viewed markers, comments and review drafts are preserved. Recognition uses names and paths. It does not detect tests embedded in production code. Supports pull request review pages on github.com; enterprise hosts are not supported. Page information is processed on your device. Only preferences are saved in local browser storage. No page data or settings are sent to the publisher. No analytics or remote code. Open source. Code and support: https://github.com/vezmenov/github-pr-file-filter Independent project, not affiliated with GitHub.
0 out of 5No ratings
Details
- Version1.1.0
- UpdatedOctober 18, 2026
- Size34.2KiB
- LanguagesEnglish
- Developer
Email
fetterdev@gmail.com - Non-traderThis developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.
Privacy
GitHub PR File Filter has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.
GitHub PR File Filter handles the following:
This developer declares that your data is
- Not being sold to third parties, outside of the approved use cases
- Not being used or transferred for purposes that are unrelated to the item's core functionality
- Not being used or transferred to determine creditworthiness or for lending purposes
Support
For help with questions, suggestions, or problems, visit the developer's support site