The Nix repo(https://github.com/NixOS/nix) has over 14k stars and over 1k
clones. I believe this project is widely used and popular enough to move
to the root now.
**Reasons for making this change:**
By default, the Unity game engine supports the importing of Blender *.blend files and converts them to FBX internally (see documentation link below). Sometimes, blender stores *.blend1 files as a backup copy of your current blender file *.blend. Due to the nature of version control, redundant *.blend1 files do not need to be committed.
**Links to documentation supporting these rule changes:**
[Unity supported file formats](https://docs.unity3d.com/Manual/3D-formats.html)
this is useful for developers that init a gleam project into an existing
git repo where the `gleam new` tool will refrain from populating the
.gitignore file. This situation may occur for users of devenv.nix or
flake.nix.
- Removed non-standard `_Release` folder;
- Added per room settings for next ags `*.crm.user`;
- Reorganized the lines in some categories with more comments.
stale-pr-message:'This PR is stale because there have been no updates in 90 days. It will close after 180 days of inactivity. Leave a comment if you want to keep it open :smile:'
close-pr-message:'This PR has been closed because it was inactive for 180 days. If you want to continue working on it, please open a new PR.'
days-before-stale:90
days-before-close:180
stale-pr-label:'stale'
exempt-pr-labels:'keep'
close-issue-reason:not_planned
ascending:true# Sort PRs by last updated date in ascending order
# Don't include the tmc-file rule if either of the following is true:
# 1. You've got TwinCAT C++ projects, as the information in the TMC-file is created manually for the C++ projects (in that case, only (manually) ignore the tmc-files for the PLC projects)
# 2. You've created a standalone PLC-project and added events to it, as these are stored in the TMC-file.
*.tmc
*.tmcRefac
*.library
*.project.~u
*.tsproj.bak
*.xti.bak
*.asm
*.core
LineIDs.dbg
LineIDs.dbg.bak
_Boot/
_CompileInfo/
_Libraries/
_ModuleInstall/
# TwinCAT C++ and shared types
# ignoring the TMC file is only useful for plain PLC programming
# as soon as shared data types (via tmc), C++ or in general TcCom-Module are used, the TMC file has to be part of the repository
# gitignore template for ECU-TEST workspaces - by TraceTronic https://tracetronic.com
# gitignore template for ecu.test workspaces - by tracetronic https://tracetronic.com
# website: https://www.ecu-test.com
# * all directories are related to the default directories, please adapt the .gitignore if you use customized
# directories
# * all directories are related to the default directories, please adapt the .gitignore if you use customized directories
# Dynamic workspace settings
# * We don't recommend to ignore the .workspace directory, because of important project specific settings
# local user settings
# * We don't recommend to ignore the .workspace directory, because of important
# * project specific settings
# * local user settings
.workspace/ETdrive.xml
.workspace/favorites.xml
.workspace/filters.xml
@@ -19,13 +19,15 @@
.workspace/tooladapter.xml
.workspace/view.xml
# optional, if your process depends on this file remove exclusion
.workspace/attributeLists.xml
.workspace/interactiveexecution.xml
.workspace/protocol.xml
.workspace/pythonlibrary.xml
# deprecated, support for older versions
.workspace/traceexplorer.xml
# Custom file formats and test dependencies
# * you can manage your artifacts also with TEST-GUIDE (https://www.test-guide.info) and reference them via Playbooks
# * you can manage your artifacts also with test.guide (https://www.test-guide.info) and reference them via Playbooks
*.arxml
*.a2l
*.dbc
@@ -36,16 +38,18 @@
# Test results and test execution related content
# * Git is not intended to store and provide test results for all iterations
# * We recommend to use TEST-GUIDE (https://www.test-guide.info) for the test report management
# * We recommend to use test.guide (https://www.test-guide.info) for the test report management
TestReports
# Report generators and templates
# * if you want to provide (f.e.) your own report generators exclude the directory here and ignore only the
# unnecessary subdirectories
# * if you want to provide (f.e.) your own report generators exclude the directory here and ignore only the unnecessary subdirectories
Templates
# optional, default for external Python libraries
PyLibs
# Exclude large binary artifacts
# * you can manage your artifacts also with TEST-GUIDE (https://www.test-guide.info) and reference them via Playbooks
# * you can manage your artifacts also with test.guide (https://www.test-guide.info) and reference them via Playbooks
Offline-FIUs
Offline-Models
Offline-SGBDs
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Christian Fickinger