Merge f81300fe73 into 7247090aa6

.github/PULL_REQUEST_TEMPLATE.md

@@ -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,18 +8,16 @@ 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
+
+Link to application or project’s homepage: TODO
+
 ### Merge and Approval Steps
-
+- [ ] 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
-Please ensure you accomplish these tasks in order to get your contribution accepted
+- [ ] Get a review and Approval from one of the maintainers
---->
-- [ ] 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.
---->

CONTRIBUTING.md

@@ -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
+- **Explain why you’re making a change**. Even if it seems self-evident, please
-  and apply to the most specific gitignore template available for the target
+  take a sentence or two to tell us why your change or addition should happen.
-  application. For example: OS-specific ignore rules like `.DS_Store` are not
+  It’s especially helpful to articulate why this change applies to *everyone*
-  accepted anywhere but their specific gitignore, `Global/macOS.gitignore` in
+  who works with the applicable technology, rather than just you or your team.
-  this case.
 
-- **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,

Deno.gitignore

@@ -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

Global/Zed.gitignore

@@ -1,10 +0,0 @@
-# Zed
-# https://zed.dev/docs/configuring-zed#settings-files
-#
-# Zed stores project settings in a .zed/ directory, similar to .vscode/.
-# By default, ignore the directory but allow commonly shared config files.
-
-.zed/*
-!.zed/settings.json
-!.zed/tasks.json
-!.zed/debug.json

Global/macOS.gitignore

@@ -6,10 +6,10 @@ __MACOSX/
 .LSOverride
 Icon[
]
 
-# Resource forks
+# Thumbnails
 ._*
 
-# Files and directories that might appear in the root of a volume
+# Files that might appear in the root of a volume
 .DocumentRevisions-V100
 .fseventsd
 .Spotlight-V100
@@ -17,15 +17,6 @@ Icon[
]
 .Trashes
 .VolumeIcon.icns
 .com.apple.timemachine.donotpresent
-.com.apple.timemachine.supported
-.PKInstallSandboxManager
-.PKInstallSandboxManager-SystemSoftware
-.hotfiles.btree
-.vol
-.file
-.disk_label*
-lost+found
-.HFS+ Private Directory Data[
]
 
 # Directories potentially created on remote AFP share
 .AppleDB
@@ -33,25 +24,3 @@ lost+found
 Network Trash Folder
 Temporary Items
 .apdisk
-
-# Mac OS 6 to 9
-Desktop DB
-Desktop DF
-TheFindByContentFolder
-TheVolumeSettingsFolder
-.FBCIndex
-.FBCSemaphoreFile
-.FBCLockFolder
-
-# Quota system
-.quota.group
-.quota.user
-.quota.ops.group
-.quota.ops.user
-
-# TimeMachine
-Backups.backupdb
-.MobileBackups
-.MobileBackups.trash
-MobileBackups.trash
-tmbootpicker.efi

KiCad.gitignore

@@ -36,8 +36,5 @@ fp-info-cache
 # Archived Backups (KiCad 6.0)
 **/*-backups/*.zip
 
-# Local git-based history (KiCad 9.0+)
-.history
-
 # Local project settings
 *.kicad_prl

Node.gitignore

@@ -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/

Python.gitignore

@@ -200,8 +200,6 @@ cython_debug/
 #   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/
-# Temporary file for partial code execution
-tempCodeRunnerFile.py
 
 # Ruff stuff:
 .ruff_cache/

Qt.gitignore

@@ -29,10 +29,8 @@ ui_*.h
 *.jsc
 Makefile*
 *build-*
-build/
 *.qm
 *.prl
-*.qmlls.ini
 
 # Qt unit tests
 target_wrapper.*

README.md

@@ -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).
-

Scala.gitignore

@@ -1,5 +1,4 @@
 *.class
-*.tasty
 *.log
 
 # virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml

SolidWorks.gitignore

@@ -1,20 +0,0 @@
-# gitignore file for a SolidWorks project
-
-# SolidWorks temporary files
-~$*.sldprt
-~$*.sldasm
-~$*.slddrw
-~$*.sld
-
-# For systems with case-sensitive (SolidWorks uses both)
-~$*.SLDPRT
-~$*.SLDASM
-~$*.SLDDRW
-~$*.SLD
-
-# SolidWorks backups and auto-recovery
-*.bak
-*.swbak
-
-# Cache of simulation results
-/simulation_results/

VisualStudio.gitignore

@@ -86,7 +86,6 @@ BenchmarkDotNet.Artifacts/
 project.lock.json
 project.fragment.lock.json
 artifacts/
-.artifacts/
 
 # ASP.NET Scaffolding
 ScaffoldingReadMe.txt

bun.gitignore

@@ -1,113 +0,0 @@
-# Logs
-logs
-*.log
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-lerna-debug.log*
-
-# database
-*.sqlite
-
-# package-json
-package-json.lock
-
-# bun deploy file
-node_modules.bun
-
-# Diagnostic reports (https://nodejs.org/api/report.html)
-report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
-
-# Runtime data
-pids
-*.pid
-*.seed
-*.pid.lock
-
-# Directory for instrumented libs generated by jscoverage/JSCover
-lib-cov
-
-# Coverage directory used by tools like istanbul
-coverage
-*.lcov
-
-# nyc test coverage
-.nyc_output
-
-# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
-.grunt
-
-# Bower dependency directory (https://bower.io/)
-bower_components
-
-# node-waf configuration
-.lock-wscript
-
-# Compiled binary addons (https://nodejs.org/api/addons.html)
-build/Release
-
-# Dependency directories
-node_modules/
-jspm_packages/
-
-# TypeScript v1 declaration files
-typings/
-
-# TypeScript cache
-*.tsbuildinfo
-
-# Optional npm cache directory
-.npm
-
-# Optional eslint cache
-.eslintcache
-
-# Microbundle cache
-.rpt2_cache/
-.rts2_cache_cjs/
-.rts2_cache_es/
-.rts2_cache_umd/
-
-# Optional REPL history
-.node_repl_history
-
-# Output of 'npm pack'
-*.tgz
-
-# Yarn Integrity file
-.yarn-integrity
-
-# dotenv environment variables file
-.env
-.env.test
-
-# parcel-bundler cache (https://parceljs.org/)
-.cache
-
-# Next.js build output
-.next
-
-# Nuxt.js build / generate output
-.nuxt
-dist
-
-# Gatsby files
-.cache/
-# Comment in the public line in if your project uses Gatsby and *not* Next.js
-# https://nextjs.org/blog/next-9-1#public-directory-support
-# public
-
-# vuepress build output
-.vuepress/dist
-
-# Serverless directories
-.serverless/
-
-# FuseBox cache
-.fusebox/
-
-# DynamoDB Local files
-.dynamodb/
-
-# TernJS port file
-.tern-port

community/Tauri.gitignore

@@ -1,12 +0,0 @@
-# Tauri
-# https://tauri.app/
-#
-# Recommended: Rust.gitignore
-
-# Rust compilation output
-# https://doc.rust-lang.org/cargo/guide/build-cache.html
-target/
-
-# WiX Toolset cache (Windows MSI installer builds)
-# https://v2.tauri.app/distribute/windows-installer/
-WixTools/

community/embedded/Microchip_MPLAB_X_IDE.gitignore

@@ -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
-
-#-----------------------------------------------------------------------------
-