| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Add .ptc to TeX.gitignore
|
| | | |/ / / / /
| |/| | | | |
| | | | | | | |
Add .ptc extension (partial toc) from titletoc package
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Add svg temporary files
|
| | | |_|_|_|_|/
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The svg package creates two temporary files for each .svg file that is
included in the document (one .pdf file and one .pdf_tex file). These
are placed into a subfolder called svg-inkscape/ by default.
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Unity: Remove exclusion for *.meta files
|
| | |\ \ \ \ \ \ \
| |/ / / / / / /
|/| | | | | | | |
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Gitignore template for Beef programming language
|
| | |\ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Merge main branch into master branch
|
| | | |\ \ \ \ \ \ \ \ |
|
| | | | | | | | | | | | |
|
| | |/ / / / / / / / / |
|
| | | |_|_|_|_|_|/ /
| |/| | | | | | | |
|
| |\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Ignore directories from the Bazel IntelliJ plugin
|
| | |/ / / / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
These directories contain the generated project files from the Bazel IntelliJ plugin. See these links for info:
https://github.com/bazelbuild/intellij/blob/8c92239f41b20dcf88a22dcb3f44b5a9bdf46a95/.gitignore
https://github.com/bazelbuild/intellij/blob/8c92239f41b20dcf88a22dcb3f44b5a9bdf46a95/base/src/com/google/idea/blaze/base/sync/data/BlazeDataStorage.java#L36
|
| |\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Adding AllowList for Go
|
| | | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
**Reasons for making this change:**
_Allowlisting with .gitignore is a technique for dealing with source trees that can have various different untracked local files such as generated output, packages installed through package managers, “working” files, config for individual developers, etc. Rather than trying to come up with some master list of all possible untracked files and add them to .gitignore, it can be easier to start by ignoring everything and then add specific directories back._
_I think the requirements for software development are changing and there is a need to offer an alternative to the denylist._
- https://jasonstitt.com/gitignore-whitelisting-patterns
- https://github.com/golang/go
Signed-off-by: kuritka <kuritka@gmail.com>
|
| |\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
[Python] Add poetry.lock
|
| | | |_|/ / / / / / /
| |/| | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
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.
This is taken from https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
|
| |\ \ \ \ \ \ \ \ \ \
| |_|/ / / / / / / /
|/| | | | | | | | | |
Update VS Code to support *.code-snippets
|
| |/ / / / / / / / / |
|
| |\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Make not to ignore *.code-workspace
|
| | | |_|_|_|/ / / /
| |/| | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
**Reasons for making this change:**
Workspace file can allow you to have an individual VS Code setting file for each project, which is useful for monorepo-based development.
You can find an example on [lit/lit/lit-next.code-workspace](https://github.com/lit/lit/blob/08f60328abf83113fe82c9d8ee43dc71f10a9b77/lit-next.code-workspace).
**Links to documentation supporting these rule changes:**
https://code.visualstudio.com/docs/editor/multi-root-workspaces#_workspace-file
|
| |\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Add files to Hugo.gitignore
|
| | | | | | | | | | | |
|
| | | |_|/ / / / / /
| |/| | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Three new files to ignore for GoHugo repositories:
- `/assets/jsconfig.json` - Quote from [JavaScript Building](https://gohugo.io/hugo-pipes/js/): "Hugo will, by default, generate a assets/jsconfig.json file that maps the imports. This is useful for navigation/intellisense help inside code editors, but if you don’t need/want it, you can turn it off."
- `hugo_stats.json` - Quote from [Post Build Resource Transformations ](https://gohugo.io/news/0.69.0-relnotes/): "The prime current use case for the above is CSS pruning in PostCSS. In simple cases you can use the templates as a base for the content filters, but that has its limitations and can be very hard to setup, especially in themed configurations. So we have added a new writeStats configuration that, when enabled, will write a file named hugo_stats.json to your project root with some aggregated data about the build, e.g. list of HTML entities published, to be used to do CSS pruning."
- `.hugo_build.lock` - Quote from [Fine Grained File Filters ](https://gohugo.io/news/0.89.0-relnotes/): "Hugo now writes an empty file named .hugo_build.lock to the root of the project when building (also when doing hugo new mypost.md and other commands that requires a build). We recommend you just leave this file alone. Put it in .gitignore or similar if you don’t want the file in your source repository."
|
| |\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Add .gitignore for Microsoft Business Central
|
| | |/ / / / / / / / |
|
| |\ \ \ \ \ \ \ \ \
| |_|_|/ / / / / /
|/| | | | | | | | |
|
| |/ / / / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | | |
with "main".
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Create Syncthing.gitignore
|
| | | | | | | | | | |
|
| | | |/ / / / / /
| |/| | | | | | |
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
doc(readme): master branch is now main
|
| |/ / / / / / / / |
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
[Node] Use real conventions
|
| | |\ \ \ \ \ \ \ \
| |/ / / / / / / /
|/| | | | | | | | |
|
| |\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Added LensStudio.gitignore (Ted Brown)
|
| | | | | | | | | | | |
|
| | | |_|_|_|_|/ / /
| |/| | | | | | | |
|
| |\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Remove nuget.config from VisualStudio.gitignore
|
| | |\ \ \ \ \ \ \ \ \
| |/ / / / / / / / /
|/| | | | | | | | | |
|
| |\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
feat(node): added `.stylelintcache` for stylelint
|
| | | |_|_|/ / / / / /
| |/| | | | | | | | |
|
| |\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
Add vuepress v2.x temp and cache directory
|
| | |/ / / / / / / / / |
|
| |\ \ \ \ \ \ \ \ \ \ |
|
| | | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
First and foremost I think that requiring such a complicated gitignore for JetBrains IDEs is a failure on JetBrains part in structuring their project setting. I also feel that it should be included in the `Python.gitignore` due to its popularity and due to the frequency of requests. A quick search for `PyCharm` PRs shows 81 closed PRs requesting it be added and if searching for `.idea` you can see many more have been requested. However I understand the maintenance burden in including it when a user can manually merge the two files themselves so I understand why the maintainers have opted to maintain it seperately.
The main problem I see is that with many people adding the `Python.gitignore` at project creation through the Github UI and the `JetBrains.gitignore` being in the Global folder and makes it less discoverable than it should be.
This PR adds a comment for people adding the `Python.gitignore` directing them to the global `JetBrains.gitignore` which should solve this issue in a way that is acceptable for the maintainers, since comment-only sections already exist for `pyenv` and `pipenv`.
|
| |\ \ \ \ \ \ \ \ \ \ \ |
|
| | | |_|_|_|_|/ / / / /
| |/| | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Reasons for making this change:
Rails dotenv ignore is not following dotenv recommendations as stated in its documentation
Links to documentation supporting these rule changes:
https://github.com/bkeepers/dotenv#what-other-env-files-can-i-use
|
| |\ \ \ \ \ \ \ \ \ \ \ |
|
