Skip to content

Provide an option to generate BUILD.bazel#22

Open
bshashank wants to merge 3 commits intotuomasr:masterfrom
bshashank:sbharadwaj/file_path_options
Open

Provide an option to generate BUILD.bazel#22
bshashank wants to merge 3 commits intotuomasr:masterfrom
bshashank:sbharadwaj/file_path_options

Conversation

@bshashank
Copy link

In my project, I already have files name build, so I'd like to generate BUILD.bazel files via pazel. This PR adds a new option:
BUILD_FILE_NAME = 'BUILD.bazel'
and setting that allows all the generated files to be named as BUILD.bazel instead of the default BUILD.

Bonus: update gitignore to ignore all bazel-* symlinks

This PR fixes #21

Testing Done:

❯ bazel test //pazel/...
INFO: Analyzed 15 targets (0 packages loaded, 0 targets configured).
INFO: Found 10 targets and 5 test targets...
INFO: Elapsed time: 0.210s, Critical Path: 0.01s
INFO: 0 processes.
INFO: Build completed successfully, 1 total action
//pazel/tests:test_bazel_rules                                  (cached) PASSED in 0.4s
//pazel/tests:test_generate_rule                                (cached) PASSED in 0.1s
//pazel/tests:test_helpers                                      (cached) PASSED in 0.1s
//pazel/tests:test_parse_imports                                (cached) PASSED in 0.1s
//pazel/tests:test_pazel_extensions                             (cached) PASSED in 0.1s

INFO: Build completed successfully, 1 total action

bshashank added 3 commits May 6, 2019 22:28
BUILD conflicts with the name 'build' on case-insensitive file-systems. pazel
should have a way for allowing the generated file name to be overriden
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Provide the ability to generate BUILD.bazel file instead of just BUILD

1 participant