azure-sdk-for-js/.gitattributes

# Don't allow people to merge changes to these generated files, because the result
# may be invalid.  You need to run "rush update" again.
pnpm-lock.yaml               merge=binary
shrinkwrap.yaml              merge=binary
npm-shrinkwrap.json          merge=binary
yarn.lock                    merge=binary


# Rush's JSON config files use JavaScript-style code comments.  The rule below prevents pedantic
# syntax highlighters such as GitHub's from highlighting these comments as errors.  Your text editor
# may also require a special configuration to allow comments in JSON.
#
# For more information, see this issue: https://github.com/Microsoft/web-build-tools/issues/1088
#
*.json            linguist-language=JSON-with-Comments

# Use unix line endings everywhere, even on Windows
* text=auto eol=lf

# Mark recordings as auto generated
**/recordings/**/*.js linguist-generated=true
**/recordings/**/*.json linguist-generated=true

# Mark generated code as auto generated
**/generated/**/*.ts linguist-generated=true
Initialize Rush repo 2019-04-04 21:44:01 +03:00			`# Don't allow people to merge changes to these generated files, because the result`
			`# may be invalid. You need to run "rush update" again.`
			`pnpm-lock.yaml merge=binary`
			`shrinkwrap.yaml merge=binary`
			`npm-shrinkwrap.json merge=binary`
			`yarn.lock merge=binary`


			`# Rush's JSON config files use JavaScript-style code comments. The rule below prevents pedantic`
			`# syntax highlighters such as GitHub's from highlighting these comments as errors. Your text editor`
			`# may also require a special configuration to allow comments in JSON.`
			`#`
			`# For more information, see this issue: https://github.com/Microsoft/web-build-tools/issues/1088`
			`#`
			`*.json linguist-language=JSON-with-Comments`

Use UNIX LF line endings everywhere, even on Windows (#10360) The new Prettier-based formatting commit hook is incompatible with Windows CRLF line endings so enforce Unix LF everywhere. The .gitattributes prior to this change causes these conversions even if core.autocrlf is false. This configuration, in contrast, works irrespective of the global git configuration. It also prevents files from being committed with Windows line endings accidentally. * Git 2.10 (release 2016-09-03) or later required * Earlier versions of git will incorrectly apply eol=lf to binary files unless explicitly called out as binary in .gitattributes * Existing working copies on Windows will not have their existing line endings corrected, and you will get `warning: CRLF will be replaced by LF in <file>` when you edit them. * To convert all of the files in an existing working copy to avoid these warnings: 1. MAKE SURE all your work is committed and pushed somewhere as a backup 2. MAKE SURE `git status` reports "nothing to commit, working tree clean" 3. Run the following from working copy root: ``` git rm --cached -r . git reset --hard ``` 2020-07-31 00:18:17 +03:00			`# Use unix line endings everywhere, even on Windows`
			`* text=auto eol=lf`
Update gitattributes to mark generated files (#6701) Generated files are collapsed by default in the diff view. This will make reviewing PRs a bit easier. 2019-12-27 23:31:39 +03:00
			`# Mark recordings as auto generated`
			`/recordings//*.js linguist-generated=true`
			`/recordings//*.json linguist-generated=true`
added github support via .gitattributes to treat generated files in PRs as do-not-display-by-default (#17139) 2021-08-26 14:39:24 +03:00
			`# Mark generated code as auto generated`
			`/generated//*.ts linguist-generated=true`