These terms cover your use of IgnoreDebugger. The short version: the tool is free, it is provided as it is, and you should check anything important against Git itself before you rely on it. The sections below spell that out.
By using this website you accept these terms. If you don't accept them, please don't use the site.
Using this website and the tool
You may use the Gitignore Debugger freely, for personal or commercial work, without payment and without creating an account. There is no licence to accept and no usage limit to keep track of.
In return, please don't:
- attempt to disrupt the site, or place deliberate automated load on it
- republish it as your own service, or present it as though you operate it
- use it for anything unlawful
No guarantee of results or fitness for a purpose
The tool is an independent re-implementation of the rules Git applies to.gitignore patterns. Its behaviour is tested against realgit check-ignore output, but it is not Git, it is not affiliated with the Git project, and it can be wrong — through a bug, a pattern nobody thought to test, or a change in a future version of Git.
So no promise is made that the results are accurate, complete or suitable for any particular purpose. Nothing here is advice about how you should configure your repository. As the about pageexplains, the tool also cannot see your repository: it knows only the path and rules you paste in, so it cannot tell you whether a file is already tracked, and it does not read nested.gitignore files, .git/info/exclude or a global core.excludesFile.
Checking the results is your responsibility
You are responsible for verifying anything the tool tells you before acting on it, and for the consequences of what you commit, ignore or delete. git check-ignore -v andgit status --ignored are the authority; use them when the answer matters.
This matters most in one direction in particular. If the tool suggests a file is ignored and it isn't, a secret can end up in a commit. Please confirm with Git before trusting an ignore rule to keep credentials, keys or private configuration out of a repository.
Content and intellectual property
The wording, design and source code of this website are the work of its author, and remain their property. You're welcome to link to any page, quote a short passage with attribution, or use what you learn here in your own projects. Please don't copy the site wholesale or reproduce substantial parts of it as your own.
What you type into the tool stays yours. No rights over it are claimed — and, as described in theprivacy policy, it never leaves your browser in the first place.
Git is a trademark of its respective owner. This site is neither affiliated with nor endorsed by the Git project, and any other product names mentioned belong to their respective owners.
Availability and changes to the service
The site is offered without any promise about availability. It may be unreachable during maintenance or a hosting problem, and features may be added, altered or removed at any time — including taking the site offline permanently — without notice. Because there is no account and no charge, there is nothing for you to cancel and no data of yours held here to lose.
Limitation of liability
The site and the tool are provided free of charge, as they are, without warranty of any kind.
To the fullest extent the law allows, the author is not liable for any loss or damage arising from your use of this site or from reliance on its output. That includes lost or overwritten work, files committed or left out of a commit, credentials exposed in a repository, and any business, revenue or data loss that follows from such an event.
Nothing in these terms limits any liability that cannot lawfully be limited.
Contact
If any part of these terms is unclear, or you believe the tool has produced an incorrect result, please get in touch. Bug reports are genuinely welcome — sending the file path and the rules you used makes the case reproducible.
Contact: admin@ignoredebugger.com
Changes to these terms
These terms may be updated as the site changes. Any revision applies from the moment it is published here, and the date at the top of the page will change with it. There is no mailing list, so re-reading this page is the only way to see a revision.