angular-cn/.gitignore

.DS_STORE

/dist/
/bazel-out
/integration/bazel/bazel-*
*.log
node_modules

# Include when developing application packages.
pubspec.lock
.c9
.idea/
.devcontainer/*
!.devcontainer/README.md
!.devcontainer/recommended-devcontainer.json
!.devcontainer/recommended-Dockerfile
.settings/
.vscode/launch.json
.vscode/settings.json
.vscode/tasks.json
*.swo
*.swp
modules/.settings
modules/.vscode
.vimrc
.nvimrc

# Don't check in secret files
*secret.js

# Ignore npm/yarn debug log
npm-debug.log
yarn-error.log

# build-analytics
.build-analytics

# rollup-test output
/modules/rollup-test/dist/

# User specific bazel settings
.bazelrc.user

# User specific ng-dev settings
.ng-dev.user*

.notes.md
baseline.json

# Ignore .history for the xyz.local-history VSCode extension
.history

# Husky
.husky/_
Tweak .gitignore file to ignore also packages symlinks. 2015-04-18 01:36:40 -04:00			`.DS_STORE`

refactor(build): simplify and modularize simplify: - use same html file for dart and JS - build benchmarks automatically when doing `gulp build` - centralize configuration modularize: - move all build tasks into separate node.js modules under `tools/build`. changes: - the `build` folder is now the `dist` folder Closes #284 2014-12-05 19:26:30 -05:00			`/dist/`
build: update and unify gitignore (#28316) PR Close #28316 2019-01-23 08:37:12 -05:00			`/bazel-out`
build(bazel): replace yarn_install(name = "npm") with @npm local_reporsitory() to speed up build (#27469) PR Close #27469 2018-12-04 19:28:58 -05:00			`/integration/bazel/bazel-*`
style: ignore *.log files (#33178) PR Close #33178 2019-10-14 16:41:12 -04:00			`*.log`
build - refactor 2014-09-18 17:56:38 -04:00			`node_modules`
Initial commit 2014-09-18 12:12:01 -04:00
			`# Include when developing application packages.`
			`pubspec.lock`
chore: add .c9 to gitignore 2014-09-19 17:55:04 -04:00			`.c9`
chore: update .gitignore for web-storm 2014-09-26 00:01:52 -04:00			`.idea/`
build: add recommended config files for VSCode remote development (#30450) Add some recommended config files to use (as is or as basis) for setting up [remote development using docker containers][1] with VSCode. This is an opt-in feature. See `.devcontainer/README.md` for more info. The configuration can be further tweaked/improved, but is a good starting point. [1]: https://code.visualstudio.com/docs/remote/containers PR Close #30450 2019-05-14 04:48:16 -04:00			`.devcontainer/*`
docs: add info on setting up VSCode remote development using docker containers (#33790) In f78bda9ff, recommended configuration files were added to be used as basis for setting up [Remote Development using docker containers][1] in VSCode. Apparently, I had forgotten to commit the corresponding `README.md` file. This commit adds `.devcontainer/README.md` with more info on Remote Development in VSCode. [1]: https://code.visualstudio.com/docs/remote/containers PR Close #33790 2019-11-13 05:01:59 -05:00			`!.devcontainer/README.md`
build: add recommended config files for VSCode remote development (#30450) Add some recommended config files to use (as is or as basis) for setting up [remote development using docker containers][1] with VSCode. This is an opt-in feature. See `.devcontainer/README.md` for more info. The configuration can be further tweaked/improved, but is a good starting point. [1]: https://code.visualstudio.com/docs/remote/containers PR Close #30450 2019-05-14 04:48:16 -04:00			`!.devcontainer/recommended-devcontainer.json`
			`!.devcontainer/recommended-Dockerfile`
chore(vscode): add jsconfig.json and remove .settings dir VSCode recognizes jsconfig.json for es6 code in the same way as it recognizes tsconfig.json for ts code. Closes #4955 2015-10-29 08:14:48 -04:00			`.settings/`
build: hide vscode settings e.g. debug launch config (#28299) PR Close #28299 2019-01-22 14:29:07 -05:00			`.vscode/launch.json`
build: make VSCode settings opt-in (#29504) PR Close #29504 2019-03-28 11:20:02 -04:00			`.vscode/settings.json`
style: Add VSCode recommended launch and task configurations (#33544) This adds a common configurations used when developing code in VSCode. Specifically it adds support for launching these targets as tasks and ind debugger. - `packages/core/test` - `packages/core/test/render3` - `packages/core/test/acceptance` PR Close #33544 2019-11-02 00:20:44 -04:00			`.vscode/tasks.json`
feat(ng-repeat): initial implementaion of ng-repeat. - adds support for content bindings via '[]'. - directives module 2014-12-05 20:44:00 -05:00			`*.swo`
fix(dev-infra): add vim .swp files to gitignore (#40094) The vim editor produces temporarily files that can end in both .swo and .swp. This commits add .swp to the .gitignore so we don't accidentaly commit temporary files. PR Close #40094 2020-12-11 15:29:25 -05:00			`*.swp`
chore: added modules/.settings to .gitignore Closes #2993 2015-07-10 20:31:32 -04:00			`modules/.settings`
tools: add .vscode to .gitignore 2015-09-10 11:33:49 -04:00			`modules/.vscode`
build: add .vimrc to .gitignore (#32253) Vim users may need to create a custom `.vimrc` when developing on the Angular project. The primary use case of this is setting the clang-format executable to `node_modules/.bin/clang-format`. PR Close #32253 2019-08-21 22:17:14 -04:00			`.vimrc`
			`.nvimrc`
chore(docs): initial dgeni docs generation Closes #261 2014-12-04 09:02:03 -05:00
refactor(benchmarks): add cloud reporter, add params - adds console and cloud reporter (via Google BigQuery). - makes parameters of tests explicit and modifiable. - removes `detect` and `ignoreGc` mode from benchpress as these can result in unstable numbers. 2015-01-09 21:00:04 -05:00			`# Don't check in secret files`
			`*secret.js`
chore(docs): initial dgeni docs generation Closes #261 2014-12-04 09:02:03 -05:00
build(aio): update .gitignore 2017-02-06 13:40:16 -05:00			`# Ignore npm/yarn debug log`
feat(gulp): adds System.register bundle task. 2015-03-23 16:18:05 -04:00			`npm-debug.log`
build(aio): update .gitignore 2017-02-06 13:40:16 -05:00			`yarn-error.log`
feat(gulp): adds System.register bundle task. 2015-03-23 16:18:05 -04:00
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672 2015-10-11 05:23:05 -04:00			`# build-analytics`
			`.build-analytics`
chore(analytics): Build hello_world, check constraints Create gulp targets to build `hello_world` and check its gzipped size against size constraints. See #5312, #5314 2015-11-19 19:08:23 -05:00
repackaging: all the repackaging changes squashed 2016-04-28 20:50:03 -04:00			`# rollup-test output`
			`/modules/rollup-test/dist/`
build: introduce remote bazel caching (#27358) This PR introduces: 1. Google Cloud Store bucket which contains build artifacts 2. Documentation on how to enable remote caching in development Each team member should download a service key. More convenient ways of authentication would be more obscure and prevent us from doing identity tracking of the produced artifacts. PR Close #27358 2018-11-28 18:34:27 -05:00
			`# User specific bazel settings`
			`.bazelrc.user`

feat(dev-infra): Add support for local user ng-dev configuration (#38701) Create a utility for loading a local user configuration object to describe local configuration values, such as skipping the commit message wizard. PR Close #38701 2020-09-03 16:53:03 -04:00			`# User specific ng-dev settings`
			`.ng-dev.user*`

test: Add script which allows running all of the profiling tests and compare results (#33186) PR Close #33186 2019-10-15 16:15:24 -04:00			`.notes.md`
			`baseline.json`
build: Ignore .history for the xyz.local-history VSCode extension (#38121) Ignore .history for the xyz.local-history VSCode extension PR Close #38121 2020-07-17 14:43:46 -04:00
			`# Ignore .history for the xyz.local-history VSCode extension`
			`.history`
build: revert back to downloading cldr-data directly rather than via npm (#39341) Revert back to downloading cldr-data directly as the npm package seems to no longer be maintained and additionally, it carries a ~350mb cost in our node modules that is unnecessarily downloaded by most developers and on CI. PR Close #39341 2020-10-20 12:01:23 -04:00
build: add husky ignored files to .gitignore (#39388) Ahead of upgrading to husky v5, adding the shell file location to .gitignore to prevent it from randomly showing up when devs checkout older branches. Beginning in v5, husky places its shell files in a directory at `.husky/_` so these are placed in the .gitignore to prevent being commited or tracked. PR Close #39388 2020-10-22 11:58:59 -04:00			`# Husky`
			`.husky/_`