mirror of
https://github.com/github/gitignore.git
synced 2026-11-05 17:44:46 +01:00
Compare commits
2
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
 Kath Hill
|
d01621805c | ||
|
Kath HillandNathan
|
42bfaa0047 |
No files matched your search
@@ -1,10 +1,3 @@
|
||||
### Link to the application or project's homepage
|
||||
|
||||
_TODO_
|
||||
<!---
|
||||
Link to the project or application's homepage.
|
||||
--->
|
||||
|
||||
### Reasons for making this change
|
||||
|
||||
_TODO_
|
||||
@@ -15,8 +8,9 @@ Please provide some background for this change.
|
||||
### Links to documentation supporting these rule changes
|
||||
|
||||
_TODO_
|
||||
|
||||
<!---
|
||||
Link to the project docs, any existing .gitignore files that project may have in its own repo, etc
|
||||
Link to the project docs, any existing .gitignore files that project may have in it's own repo, etc
|
||||
--->
|
||||
|
||||
### If this is a new template
|
||||
@@ -24,13 +18,6 @@ Link to the project docs, any existing .gitignore files that project may have in
|
||||
Link to application or project’s homepage: TODO
|
||||
|
||||
### Merge and Approval Steps
|
||||
|
||||
<!---
|
||||
Please ensure you accomplish these tasks in order to get your contribution accepted
|
||||
--->
|
||||
- [ ] I have read the [contribution guidelines](https://github.com/github/gitignore/tree/main?tab=readme-ov-file#contributing-guidelines) and understand my PR will be closed if it doesn't meet these guidelines
|
||||
|
||||
<!---
|
||||
Once done, please wait for a GitHub maintainer to review your PR and if necessary,
|
||||
work with them to address any findings.
|
||||
--->
|
||||
- [ ] Confirm that you've read the [contribution guidelines](https://github.com/github/gitignore/tree/main?tab=readme-ov-file#contributing-guidelines) and ensured your PR aligns
|
||||
- [ ] Ensure CI is passing
|
||||
- [ ] Get a review and Approval from one of the maintainers
|
||||
+11
-21
@@ -2,46 +2,36 @@
|
||||
|
||||
We’d love you to help us improve this project. To help us keep this collection
|
||||
high quality, we request that contributions adhere to the following guidelines.
|
||||
Any contributions that don't meet these guidelines will be closed.
|
||||
|
||||
- **Provide a link to the application or project’s homepage**. Unless it’s
|
||||
extremely popular, there’s a chance the maintainers don’t know about or use
|
||||
the language, framework, editor, app, or project your change applies to.
|
||||
|
||||
- **Provide a reason for making this change**. Even if it seems self-evident,
|
||||
please take a sentence or two to tell us why your change or addition should
|
||||
happen. It’s especially helpful to articulate why this change applies to
|
||||
*everyone* who works with the applicable technology, rather than just you or
|
||||
your team.
|
||||
|
||||
- **Provide links to documentation** supporting the change you’re making.
|
||||
Current, canonical documentation mentioning the files being ignored is best.
|
||||
If documentation isn’t available to support your change, do the best you can
|
||||
to explain what the files being ignored are for.
|
||||
|
||||
- **Keep scope as limited as possible**. Changes should be as small as possible
|
||||
and apply to the most specific gitignore template available for the target
|
||||
application. For example: OS-specific ignore rules like `.DS_Store` are not
|
||||
accepted anywhere but their specific gitignore, `Global/macOS.gitignore` in
|
||||
this case.
|
||||
- **Explain why you’re making a change**. Even if it seems self-evident, please
|
||||
take a sentence or two to tell us why your change or addition should happen.
|
||||
It’s especially helpful to articulate why this change applies to *everyone*
|
||||
who works with the applicable technology, rather than just you or your team.
|
||||
|
||||
- **Only modify *one template* per pull request**. This helps keep pull
|
||||
- **Please consider the scope of your change**. If your change specific to a
|
||||
certain language or framework, then make sure the change is made to the
|
||||
template for that language or framework, rather than to the template for an
|
||||
editor, tool, or operating system.
|
||||
|
||||
- **Please only modify *one template* per pull request**. This helps keep pull
|
||||
requests and feedback focused on a specific project or technology.
|
||||
|
||||
- **Add new rules to the most appropriate existing section**. Please ensure
|
||||
your contribution does not create duplicate sections or add rules in
|
||||
unrelated sections.
|
||||
|
||||
- **No duplicate rules**. It's easy to do, but it creates confusion and
|
||||
introduces the risk of one or the other being missed in an update.
|
||||
|
||||
In general, the more you can do to help us understand the change you’re making,
|
||||
the more likely we’ll be to accept your contribution quickly.
|
||||
|
||||
If a template is mostly a list of files installed by a particular version of
|
||||
some software (e.g. a PHP framework) then it's brittle and probably no more
|
||||
helpful than a simple `ls`. If it's not possible to curate a small set of
|
||||
useful rules, then the template is not a good fit for this collection.
|
||||
useful rules, then the template might not be a good fit for this collection.
|
||||
|
||||
Please also understand that we can’t list every tool that ever existed.
|
||||
Our aim is to curate a collection of the *most common and helpful* templates,
|
||||
|
||||
@@ -1,11 +0,0 @@
|
||||
# Deno
|
||||
# https://deno.com/
|
||||
|
||||
# Cache directory (when using project-local DENO_DIR)
|
||||
# https://docs.deno.com/runtime/fundamentals/setup/#deno_dir
|
||||
.deno/
|
||||
|
||||
# Coverage reports
|
||||
# https://docs.deno.com/runtime/reference/cli/coverage/
|
||||
coverage/
|
||||
*.lcov
|
||||
+2
-1
@@ -92,8 +92,9 @@ dist
|
||||
# vuepress build output
|
||||
.vuepress/dist
|
||||
|
||||
# vuepress v2.x temp directory
|
||||
# vuepress v2.x temp and cache directory
|
||||
.temp
|
||||
.cache
|
||||
|
||||
# Sveltekit cache directory
|
||||
.svelte-kit/
|
||||
|
||||
@@ -36,9 +36,6 @@ We support a collection of templates, organized in this way:
|
||||
|
||||
## What makes a good template?
|
||||
|
||||
First and foremost, a template contribution must adhere to our
|
||||
[Contributing Guidelines](CONTRIBUTING.md).
|
||||
|
||||
A template should contain a set of rules to help Git repositories work with a
|
||||
specific programming language, framework, tool or environment.
|
||||
|
||||
@@ -64,7 +61,33 @@ include your language, tool, or project, it’s not because it’s not awesome.
|
||||
|
||||
## Contributing guidelines
|
||||
|
||||
Please see our [Contributing Guidelines](CONTRIBUTING.md).
|
||||
We’d love for you to help us improve this project. To help us keep this collection
|
||||
high quality, we request that contributions adhere to the following guidelines.
|
||||
|
||||
- **Provide a link to the application or project’s homepage**. Unless it’s
|
||||
extremely popular, there’s a chance the maintainers don’t know about or use
|
||||
the language, framework, editor, app, or project your change applies to.
|
||||
|
||||
- **Provide links to documentation** supporting the change you’re making.
|
||||
Current, canonical documentation mentioning the files being ignored is best.
|
||||
If documentation isn’t available to support your change, do the best you can
|
||||
to explain what the files being ignored are for.
|
||||
|
||||
- **Explain why you’re making a change**. Even if it seems self-evident, please
|
||||
take a sentence or two to tell us why your change or addition should happen.
|
||||
It’s especially helpful to articulate why this change applies to _everyone_
|
||||
who works with the applicable technology, rather than just you or your team.
|
||||
|
||||
- **Please consider the scope of your change**. If your change is specific to a
|
||||
certain language or framework, then make sure the change is made to the
|
||||
template for that language or framework, rather than to the template for an
|
||||
editor, tool, or operating system.
|
||||
|
||||
- **Please only modify _one template_ per pull request**. This helps keep pull
|
||||
requests and feedback focused on a specific project or technology.
|
||||
|
||||
In general, the more you can do to help us understand the change you’re making,
|
||||
the more likely we’ll be to accept your contribution quickly.
|
||||
|
||||
## Versioned templates
|
||||
|
||||
@@ -130,4 +153,3 @@ by automatically forking the project and prompting to send a pull request too.
|
||||
## License
|
||||
|
||||
[CC0-1.0](./LICENSE).
|
||||
|
||||
+222
@@ -0,0 +1,222 @@
|
||||
# Byte-compiled / optimized / DLL files
|
||||
__pycache__/
|
||||
*.py[codz]
|
||||
*$py.class
|
||||
|
||||
# C extensions
|
||||
*.so
|
||||
|
||||
# Distribution / packaging
|
||||
.Python
|
||||
build/
|
||||
develop-eggs/
|
||||
dist/
|
||||
downloads/
|
||||
eggs/
|
||||
.eggs/
|
||||
lib/
|
||||
lib64/
|
||||
parts/
|
||||
sdist/
|
||||
var/
|
||||
wheels/
|
||||
share/python-wheels/
|
||||
*.egg-info/
|
||||
.installed.cfg
|
||||
*.egg
|
||||
MANIFEST
|
||||
|
||||
# PyInstaller
|
||||
# Usually these files are written by a python script from a template
|
||||
# before PyInstaller builds the exe, so as to inject date/other infos into it.
|
||||
*.manifest
|
||||
*.spec
|
||||
|
||||
# Installer logs
|
||||
pip-log.txt
|
||||
pip-delete-this-directory.txt
|
||||
|
||||
# Unit test / coverage reports
|
||||
htmlcov/
|
||||
.tox/
|
||||
.nox/
|
||||
.coverage
|
||||
.coverage.*
|
||||
.cache
|
||||
nosetests.xml
|
||||
coverage.xml
|
||||
*.cover
|
||||
*.py.cover
|
||||
.hypothesis/
|
||||
.pytest_cache/
|
||||
cover/
|
||||
|
||||
# Translations
|
||||
*.mo
|
||||
*.pot
|
||||
|
||||
# Django stuff:
|
||||
*.log
|
||||
local_settings.py
|
||||
db.sqlite3
|
||||
db.sqlite3-journal
|
||||
|
||||
# Flask stuff:
|
||||
instance/
|
||||
.webassets-cache
|
||||
|
||||
# Scrapy stuff:
|
||||
.scrapy
|
||||
|
||||
# Sphinx documentation
|
||||
docs/_build/
|
||||
|
||||
# PyBuilder
|
||||
.pybuilder/
|
||||
target/
|
||||
|
||||
# Jupyter Notebook
|
||||
.ipynb_checkpoints
|
||||
|
||||
# IPython
|
||||
profile_default/
|
||||
ipython_config.py
|
||||
|
||||
# pyenv
|
||||
# For a library or package, you might want to ignore these files since the code is
|
||||
# intended to run in multiple environments; otherwise, check them in:
|
||||
# .python-version
|
||||
|
||||
# pipenv
|
||||
# According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
|
||||
# However, in case of collaboration, if having platform-specific dependencies or dependencies
|
||||
# having no cross-platform support, pipenv may install dependencies that don't work, or not
|
||||
# install all needed dependencies.
|
||||
#Pipfile.lock
|
||||
|
||||
# UV
|
||||
# Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
|
||||
# This is especially recommended for binary packages to ensure reproducibility, and is more
|
||||
# commonly ignored for libraries.
|
||||
#uv.lock
|
||||
|
||||
# poetry
|
||||
# Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
|
||||
# This is especially recommended for binary packages to ensure reproducibility, and is more
|
||||
# commonly ignored for libraries.
|
||||
# https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
|
||||
#poetry.lock
|
||||
#poetry.toml
|
||||
|
||||
# pdm
|
||||
# Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
|
||||
# pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
|
||||
# https://pdm-project.org/en/latest/usage/project/#working-with-version-control
|
||||
#pdm.lock
|
||||
#pdm.toml
|
||||
.pdm-python
|
||||
.pdm-build/
|
||||
|
||||
# pixi
|
||||
# Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
|
||||
#pixi.lock
|
||||
# Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
|
||||
# in the .venv directory. It is recommended not to include this directory in version control.
|
||||
.pixi
|
||||
|
||||
# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
|
||||
__pypackages__/
|
||||
|
||||
# Celery stuff
|
||||
celerybeat-schedule
|
||||
celerybeat.pid
|
||||
|
||||
# SageMath parsed files
|
||||
*.sage.py
|
||||
|
||||
# Environments
|
||||
.env
|
||||
.envrc
|
||||
.venv
|
||||
env/
|
||||
venv/
|
||||
ENV/
|
||||
env.bak/
|
||||
venv.bak/
|
||||
|
||||
# Spyder project settings
|
||||
.spyderproject
|
||||
.spyproject
|
||||
|
||||
# Rope project settings
|
||||
.ropeproject
|
||||
|
||||
# mkdocs documentation
|
||||
/site
|
||||
|
||||
# mypy
|
||||
.mypy_cache/
|
||||
.dmypy.json
|
||||
dmypy.json
|
||||
|
||||
# Pyre type checker
|
||||
.pyre/
|
||||
|
||||
# pytype static type analyzer
|
||||
.pytype/
|
||||
|
||||
# Cython debug symbols
|
||||
cython_debug/
|
||||
|
||||
# PyCharm
|
||||
# JetBrains specific template is maintained in a separate JetBrains.gitignore that can
|
||||
# be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
|
||||
# and can be added to the global gitignore or merged into this file. For a more nuclear
|
||||
# option (not recommended) you can uncomment the following to ignore the entire idea folder.
|
||||
#.idea/
|
||||
|
||||
# Abstra
|
||||
# Abstra is an AI-powered process automation framework.
|
||||
# Ignore directories containing user credentials, local state, and settings.
|
||||
# Learn more at https://abstra.io/docs
|
||||
.abstra/
|
||||
|
||||
# Visual Studio Code
|
||||
# Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore
|
||||
# that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
|
||||
# and can be added to the global gitignore or merged into this file. However, if you prefer,
|
||||
# you could uncomment the following to ignore the entire vscode folder
|
||||
# .vscode/
|
||||
|
||||
# Ruff stuff:
|
||||
.ruff_cache/
|
||||
|
||||
# PyPI configuration file
|
||||
.pypirc
|
||||
|
||||
# Cursor
|
||||
# Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
|
||||
# exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
|
||||
# refer to https://docs.cursor.com/context/ignore-files
|
||||
.cursorignore
|
||||
.cursorindexingignore
|
||||
|
||||
# Marimo
|
||||
marimo/_static/
|
||||
marimo/_lsp/
|
||||
__marimo__/
|
||||
|
||||
*.save
|
||||
persistent
|
||||
|
||||
errors.txt
|
||||
log.txt
|
||||
progressive_download.txt
|
||||
traceback.txt
|
||||
*.bak
|
||||
*.1.bak
|
||||
*.rpyc
|
||||
.vscode/
|
||||
.idea/
|
||||
cache/
|
||||
game/saves/navigation.json
|
||||
@@ -1,5 +1,4 @@
|
||||
*.class
|
||||
*.tasty
|
||||
*.log
|
||||
|
||||
# virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml
|
||||
|
||||
@@ -1,27 +0,0 @@
|
||||
#=============================================================================
|
||||
# Microchip MPLAB X IDE .gitignore file.
|
||||
#
|
||||
# MPLABX: https://www.microchip.com/en-us/tools-resources/develop/mplab-x-ide
|
||||
#
|
||||
# MPLABX Version Control:-
|
||||
# https://developerhelp.microchip.com/xwiki/bin/view/software-tools/ides/x/version-control/working-with-version-control/
|
||||
#-----------------------------------------------------------------------------
|
||||
|
||||
# MPLAB X (NetBeans) Project files
|
||||
**/*.X/nbproject/private/
|
||||
**/*.X/nbproject/Makefile-*
|
||||
**/*.X/nbproject/Package-*
|
||||
!**/*.X/nbproject/*.xml
|
||||
|
||||
# MPLAB X Generated Files and Build Output
|
||||
**/*.X/.generated_files/
|
||||
**/*.X/build/
|
||||
**/*.X/dist/
|
||||
**/*.X/debug/
|
||||
|
||||
# MPLAB Code Configurator (MCC)
|
||||
**/*.X/mcc_generated_files/
|
||||
**/*.X/mcc-manifest-*.yml
|
||||
|
||||
#-----------------------------------------------------------------------------
|
||||
|
||||
Reference in new issue
Block a user