We shouldn't ignore -cache.lib files, because it causes missing components in your schema
http://kicad-pcb.org/help/file-formats/ specifically mentions this:
> `-cache.lib`: … a local copy of all the symbols used in the corresponding schematic, so that when the folder containing a KiCad project is copied to a different PC, the schematic can still be opened and printed and will still look the same as the original draughtsperson intended - even if that other PC does not have those symbols in its main libraries (or has symbols that coincidentally have the same name but are completely different).
If checked the option "Always create backup copy" under Settings -> Save within Microsoft Word 2016 on macOS, when editing a docx file, a folder named as same as docx file name(without ext) will be created and placed a docx backup file named "Backup of DOCX_ORIGINAL_FILENAME.docx".
Add extra commented section to use when using Gradle or Maven auto-import.
These are mentioned in the original reference for optional excludes (https://intellij-support.jetbrains.com/hc/en-us/articles/206544839).
If this would be better as a separate, non-commented ignore file, let me know and I will resubmit.
http://www.perl6.org
Just a start. Perl 6 creates these directories to
store pre-compiled versions of modules.
Perl 6 doesn't have a gitignore template yet, and it
doesn't use the same build and installation system as
Perl (5).
2016-10-25 23:19:42 -04:00
42 changed files with 272 additions and 144 deletions
This document outlines the additional metadata that can be associated with a gitignore template, and how tools can consume this metadata.
## Metadata Location
To add additional metadata to a gitignore template, add a new file to the same directory, with the matching name but ending in `yml`.
For example:
- for `C.gitignore` the associated metadata will be stored in `C.yml`
- for `Global/JetBrains.gitignore` the metadata file will be `Global/JetBrains.gitignore`
## Supported Fields
The structure of these files is still being settled upon, but for the moment these are some proposed entries.
#### `aliases`
Some templates can be used to represent a number of different situations, and rather than duplicating files on disk and needing to keep these in sync, we can store a list of these entries as metadata.
For example, JetBrains has a unified gitignore template that can be applied to all of their IDEs. Previously these were stored as comments in the header:
```
# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio and WebStorm
```
These values can be represented as metadata, so that tools consuming this repository can use these entries as matches if the user is searching for a specific product:
```yaml
aliases:
- IntelliJ
- RubyMine
- PhpStorm
- AppCode
- PyCharm
- CLion
- Android Studio
- WebStorm
- Rider
```
#### `editors`
There are a number of editors out there that support working with different languages. Rather than baking every editor's rules in every language that is supported, a list of additional templates that might be of interest
```yaml
editors:
- Global/JetBrains.gitignore
- Global/VisualStudioCode.gitignore
```
#### `reference`
Some ecosystems have up-to-date documentation about things that are necessary to exclude from version control. To associate this with a template, this could be stored as a key-value pair in metadata:
This element is inspired by the [`DefinitelyTyped`](https://github.com/DefinitelyTyped/DefinitelyTyped) project, allowing community members to opt-in to reviewing templates when a pull request is opened. This helps to share the review load and credit people who have been helpful with reviews.
```yaml
reviewers:
- @shiftkey
```
A friendly name can be provided alongside the GitHub account name.
```yaml
reviewers:
- Brendan Forster (@shiftkey)
```
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.