pulumi/.gitignore

*.swp
/vendor/
**/node_modules/
**/.vscode/
coverage.cov
*.coverprofile
**/dist

/.idea/
*.iml

# Go tests run "in tree" and this folder will linger if they fail (the integration test framework cleans
# it up when they pass.)
**/command-output/
Gitignore *.swp files 2016-11-16 18:28:46 +01:00			`*.swp`
Revert "The Go vendoring saga continues" This reverts commit f939651c64409fb168911f1271de5b86840e4602. This particular saga appears to never end... 2017-08-02 02:51:38 +02:00			`/vendor/`
Add license fields to package.json. (#1656) 2018-07-25 01:10:13 +02:00			`**/node_modules/`
Fix a couple of issues when projecting Protobuf and UNKNOWN in Python (#1468) * Fix a few issues with the Python language host 1. Fix an issue where the UNKNOWN sentinel was leaking into user programs 2. Fix an issue where Protobuf types were leaking into user programs In fixing this issues I also added a framework for writing tests against the Python SDK. * License headers, and adopt a more idiomatic testing pattern * Additional idiomatic Python * That's what I get for trying to be fancy (Travis CI python version is very old and does not respect this form) * CR feedback: use more comprehensions, typo fix * Break a circular dependency between resource, runtime.resource, and runtime.rpc * Don't check in .vscode * CR: sort inputs, rename global variable, add a test for CustomResource serialization * Remove accidental code duplication 2018-06-07 01:09:07 +02:00			`**/.vscode/`
Add Go code coverage reports to nightly tests Adds a make task to generate code coverage for all Go sources. That make task re-runs the tests, and can be fairly expensive, so it is enabled only in the nightly tests for now. Part of #206. 2017-06-24 00:11:20 +02:00			`coverage.cov`
			`*.coverprofile`
Use Pipenv to manage Python environments (#1553) * Use Pipenv to manage Python environments * Rename PIPENV_ARGS to PIPENV_PYTHON_VERSION to avoid confusion. Also remove two unused variables 2018-06-22 03:01:23 +02:00			`**/dist`
Sketch a `mu build` command and its scaffolding This adds a bunch of general scaffolding and the beginning of a `build` command. The general engineering scaffolding includes: * Glide for dependency management. * A Makefile that runs govet and golint during builds. * Google's Glog library for logging. * Cobra for command line functionality. The Mu-specific scaffolding includes some packages: * mu/pkg/diag: A package for compiler-like diagnostics. It's fairly barebones at the moment, however we can embellish this over time. * mu/pkg/errors: A package containing Mu's predefined set of errors. * mu/pkg/workspace: A package containing workspace-related convenience helpers. in addition to a main entrypoint that simply wires up and invokes the CLI. From there, the mu/cmd package takes over, with the Cobra-defined CLI commands. Finally, the mu/pkg/compiler package actually implements the compiler behavior. Or, it will. For now, it simply parses a JSON or YAML Mufile into the core mu/pkg/api types, and prints out the result. 2016-11-15 20:30:34 +01:00
meta: Ignore IntellJ IDEA project files 2018-06-22 01:05:28 +02:00			`/.idea/`
			`*.iml`

Don't dirty work tree when running tests Because we run our golang integration tests "in tree" (due to the need to be under $GOPATH and have a vendor folder around), the "command-output" folder was getting left behind, dirtying the worktree after building. This change does two things: 1. On a succecssful run, remove the folder. 2. Ignore the folder via .gitignore (this way if a test fails and you do `git add .` you don't end up commiting this folder). 2018-06-15 00:58:37 +02:00			`# Go tests run "in tree" and this folder will linger if they fail (the integration test framework cleans`
			`# it up when they pass.)`
			`**/command-output/`