**Reasons for making this change:**
PuTTYgen is a widely used alternative to OpenSSH under Windows.
This rule allows private keys ignoring.
If this is a new template:
- **Link to application or project’s homepage**: https://www.chiark.greenend.org.uk/~sgtatham/putty/
From the Eclipse Documentation: "Make sure that the .project and .classpath files are under version control. These files must be stored in the repository so that other users checking out the projects for the first time will get the correct type of project and will get the correct Java build path." - http://wiki.eclipse.org/FAQ_How_do_I_set_up_a_Java_project_to_share_in_a_repository%3F
**Reasons for making this change:**
The file `replstate.xml` contains the history of the Clojure REPL
that Cursive adds to IntelliJ. Obviously that's user-specific,
and not relevant to other users.
**Links to documentation supporting these rule changes:**
This file is not well-documented, but in cursive-ide/cursive#1325,
the Cursive developers state that this is the REPL history file,
and that deleting it is acceptable troubleshooting if it's
causing trouble.
In newer versions of the IntelliJ platform (such as the one used for Rider), the .idea files are now placed in a subdirectory of the same, named after the current project (such as ".idea/.idea.Everlook/.idea/workspace.xml"). Adding a double-star pattern to these folder rules will also ignore these new files and maintain backwards compatibility with previous revisions of this file.
The IPython Notebook is now known as the Jupyter Notebook (see http://ipython.org/notebook.html). Jupyter ignore values are already found in the Python.gitignore.
The PSoC is a popular microcontroller and the PSoC Creator is a great IDE that deserves a .gitignore so it's easier for people to share the _neccessary_ files for collaboration.
>not affiliated
This file as documentation (which seems lacking) states is used for calling custom Maven goals from the IDE.
Ignoring this file was a source much confusion in few projects (mapping Run action to custom goals... etc etc)
Also this file does anything worth ignoring
Added by #145
Exclusion of `nbactions.xml` from `.gitgnore` should be discussed.
Visual Studio Code has a few files that can be placed into the workspace
in order to share settings across users. Settings.json is for project
specific overrides. Tasks.json is for executable tasks (build, gulp, etc.)
While launch.json is for debugging specific tasks.
The server-auth-dir is where Emacs stores authentication files for Emacs
servers (running over TCP). These are (usually) ephemeral in nature, and
should be ignored.
Cadence Virtuoso is a commercial EDA tool used for custom IC (ASIC) design. This gitignore file
blacklists database lock files, the contents of run directories for layout versus schematic and
design rule checks as well as log files for a selection of tools inside the package.
Updated the tags ignore to include the .tags file. The main reason behind this is because Atom's symbols-view (https://atom.io/packages/symbols-view) supports tags/.tags/TAGS/.TAGS. Therefore, I thought it was a good idea to add the .tags/.TAGS to the ignore list.
* master: (24 commits)
Add ignore for npm debug log files
Add KiCad ignore for .bck and .kicad_pcb-bak
Correct capitalisation of LightSwitch and omit generated.parameters.xml
Add newline at EOF
Add ignores for Visual Studio Lightswitch build output
Adding optional ignore proposal for wwwroot folder
Ignore NCrunch temporary files.
Update Dart.gitignore
Added .stack-work/ directory to Haskell .gitignore.
add Android Studio to the covers list
Ignore Default RSpec State File
Ignore *.auxlock files created by TikZ in TeX
Ignore files created by `\tikzexternalize`
Update Typo3.gitignore for CMS v6.2
[ObjC][Swift] Ignore Xcode SCM blueprint files
include preamble files generated by mylatexformat package
Add .jar, .exe and .msi
Remove .SRCINFO (and old .AURINFO) from .gitignore
Add CMakeScripts directory
ignore OAuth2 token
...
Conflicts:
Objective-C.gitignore
Swift.gitignore
This new version adds:
- fsdb waveforms
- simv.db.dir/ directory for VHDL top configs
- ucli.key
- vc_hdrs.h
- Also added a few comments about where each one of the files come from.
In addition to `.Spotlight-V100` and `.Trashes`, the following dotfiles
may appear at the root of all OSX volumes (not just external disks):
- `.DocumentRevisions-V100`: auto-save and versions storage
- `.fseventsd`: file system event storage
- `.Temporaryitems`: temp directory used by some applications instead of
/tmp and /var/tmp
- `.VolumeIcon.icns`: storage of custom icon for volume, if set
Fixes#1217.
Once again ignore .classpath and .project in the Eclipse template. This has
been requested in multiple PRs such as #1338 and #1221 and is essentially a
reversion of #805. I copy the explanation for this change from the discussion
in #1217 by @segfly:
*In short*:
I can't point to any counter-documentation off the top of my head. I just know
from experience these files pollute a project's repo without adding value
- that is, unless everyone contributing is using Eclipse and no-one is using
dependency management. And even then, the guidance provided by the eclipse docs
is bad advice.
*In Long*:
The .classpath file is used by Eclipse to maintain the project's classpath
during automatic compile (every save of a file). In the olden days, one would
manually configure the project within the Eclipse UI and include all the
dependent jars necessary to compile your project. Eclipse then wrote that
configuration out to the .classpath file.
In theory, this file could be shared with others so they did not have to
manually configure their eclipse classpath. In practice, I never saw it work
out quite so well due to eventual bloating of the classpath with needless jars
or jars that only existed on one person's machine. Mind you, many people back
then also used to check their dependent jars into version control along with
their source.
Dependency management tools like Gradle and Maven have done away with all that
of course. But they also integrate nicely with Eclipse and manage the project
classpath dynamically. The .classpath file is basically rebuilt based on
changes to the build.gradle file or pom.xml file. Effectively, this renders the
whole point of checking in the .classpath moot as it is easily rebuilt by the
Maven or Gradle plugin.
The .project file is another animal completely. It basically describes what
plugins should be applied to the project as configured in the Eclipse UI. Again
the theory is it could be shared and creates a happy world. But due to
different eclipse versions people may have, different plugins installed, etc.
sharing the .project file actually causes more issues. And I've seen many
projects unable to open due to a bad .project file - requiring one to delete it
anyway (which then of course, when someone recreates it, they inevitably check
it in over the old one and end up breaking someone else's environment).
The bottom line is, regardless of what the eclipse documentation says, these
are very much internal configuration files for eclipse and best left out of
a repo.
