buildifier: found 44 format issues in your WORKSPACE, BUILD and *.bzl files

If this repo uses a pre-commit hook, then you should install it. Otherwise, please download buildifier 7.3.1 and run the following command in your workspace:

buildifier WORKSPACE build_test/build.bzl cc_embed_data/BUILD cc_embed_data/cc_embed_data.bzl cc_embed_data/cc_embed_data_deps.bzl css_js/BUILD css_js/css_js.bzl css_js/css_js_deps.bzl fail_test/fail_test.bzl graphviz/graphviz.bzl latex/BUILD latex/git_stamp.bzl latex/git_stamp_deps.bzl latex/latex.bzl latex/ref_test.bzl latex/repo.bzl latex/role_call_test.bzl parser/BUILD parser/parser.bzl proto_api/BUILD proto_api/proto_api.bzl repositories/aws-c-cal.bzl repositories/aws-c-common.bzl repositories/aws-c-compression.bzl repositories/aws-c-io.bzl repositories/aws-checksums.bzl repositories/aws-sdk-cpp.bzl repositories/repositories.bzl status_repository/repo.bzl tests/BUILD tests/build_test_test.bzl tests/cc_embed_data_test.bzl tests/css_js_test.bzl tests/detex_test.bzl tests/fail_test.bzl tests/gen_dot_test.bzl tests/git_stamp_test.bzl tests/latex_ref_test_test.bzl tests/parser_test.bzl tests/role_call_test_test.bzl tests/spell_test_test.bzl tests/tex_to_pdf_test.bzl text/BUILD text/spelling.bzl

buildifier: found 147 lint issues in your WORKSPACE, BUILD and *.bzl files

WORKSPACE:46:69: load: Loaded symbol "com_github_aws_sdk" is unused. Please remove it.
To disable the warning, add '@unused' in a comment.
WORKSPACE:116:1: no-effect: Expression result is not used. Docstrings should be the first statements of a file or a function (they may follow comment lines).
cc_embed_data/cc_embed_data.bzl:79:9: rule-impl-return: Avoid using the legacy provider syntax.
cc_embed_data/cc_embed_data.bzl:103:27: uninitialized: Variable "process" may not have been initialized.
cc_embed_data/cc_embed_data.bzl:135:40: uninitialized: Variable "process" may not have been initialized.
cc_embed_data/cc_embed_data.bzl:138:23: uninitialized: Variable "process" may not have been initialized.
cc_embed_data/cc_embed_data_deps.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
css_js/css_js_deps.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
fail_test/fail_test.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
fail_test/fail_test.bzl:37:5: list-append: Prefer using ".append()" to adding a single element list.
fail_test/fail_test.bzl:41:5: list-append: Prefer using ".append()" to adding a single element list.
fail_test/fail_test.bzl:57:5: list-append: Prefer using ".append()" to adding a single element list.
latex/git_stamp.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
latex/git_stamp.bzl:34:9: print: "print()" is a debug function and shouldn't be submitted.
latex/git_stamp_deps.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
latex/latex.bzl:34:5: unused-variable: Variable "interpreter" is unused. Please remove it.
latex/latex.bzl:61:9: print: "print()" is a debug function and shouldn't be submitted.
latex/latex.bzl:186:5: unused-variable: Variable "interpreter" is unused. Please remove it.
latex/latex.bzl:231:7: print: "print()" is a debug function and shouldn't be submitted.
latex/ref_test.bzl:66:30: list-append: Prefer using ".append()" to adding a single element list.
latex/repo.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
latex/repo.bzl:48:22: print: "print()" is a debug function and shouldn't be submitted.
latex/repo.bzl:49:19: print: "print()" is a debug function and shouldn't be submitted.
latex/role_call_test.bzl:70:5: list-append: Prefer using ".append()" to adding a single element list.
latex/role_call_test.bzl:71:5: list-append: Prefer using ".append()" to adding a single element list.
parser/parser.bzl:84:9: print: "print()" is a debug function and shouldn't be submitted.
parser/parser.bzl:87:9: print: "print()" is a debug function and shouldn't be submitted.
parser/parser.bzl:97:9: list-append: Prefer using ".append()" to adding a single element list.
parser/parser.bzl:109:9: list-append: Prefer using ".append()" to adding a single element list.
parser/parser.bzl:116:9: list-append: Prefer using ".append()" to adding a single element list.
proto_api/proto_api.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
proto_api/proto_api.bzl:42:9: list-append: Prefer using ".append()" to adding a single element list.
proto_api/proto_api.bzl:50:9: list-append: Prefer using ".append()" to adding a single element list.
repositories/CommonCrypto.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/CommonCrypto.bzl:4:1: function-docstring: The function "BUILD" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/CommonCrypto.bzl:4:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.cc_library" on line 71.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/aws-c-auth.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/aws-c-auth.bzl:3:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.filegroup" on line 17.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/aws-c-cal.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/aws-c-cal.bzl:4:1: function-docstring: The function "BUILD" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/aws-c-cal.bzl:4:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.filegroup" on line 68.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/aws-c-common.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/aws-c-common.bzl:5:1: function-docstring: The function "BUILD" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/aws-c-common.bzl:5:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.filegroup" on line 164.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/aws-c-compression.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/aws-c-compression.bzl:3:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.filegroup" on line 20.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/aws-c-event-stream.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/aws-c-event-stream.bzl:3:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.filegroup" on line 20.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/aws-c-http.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/aws-c-http.bzl:3:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.cc_library" on line 34.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/aws-c-io.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/aws-c-io.bzl:4:1: function-docstring: The function "BUILD" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/aws-c-io.bzl:4:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.filegroup" on line 120.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/aws-c-mqtt.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/aws-c-mqtt.bzl:3:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.filegroup" on line 20.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/aws-c-s3.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/aws-c-s3.bzl:3:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.filegroup" on line 20.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/aws-c-sdkutils.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/aws-c-sdkutils.bzl:3:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.filegroup" on line 17.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/aws-checksums.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/aws-checksums.bzl:4:1: function-docstring: The function "BUILD" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/aws-checksums.bzl:4:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.cc_library" on line 72.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/aws-crt-cpp.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/aws-crt-cpp.bzl:6:1: function-docstring: The function "BUILD" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/aws-crt-cpp.bzl:6:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.filegroup" on line 49.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/aws-s2n-tls.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/aws-s2n-tls.bzl:3:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.cc_library" on line 34.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/aws-sdk-cpp.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/aws-sdk-cpp.bzl:6:1: unnamed-macro: The macro "flag_set" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.config_setting" on line 13.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_flag_set").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/aws-sdk-cpp.bzl:13:5: no-effect: Expression result is not used. Use a for-loop instead of a list comprehension.
repositories/aws-sdk-cpp.bzl:37:1: function-docstring: The function "BUILD" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/aws-sdk-cpp.bzl:37:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "flag_set" on line 207.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/aws-sdk-cpp.bzl:73:13: print: "print()" is a debug function and shouldn't be submitted.
repositories/compare_cc_deps_test.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/compare_cc_deps_test.bzl:38:9: print: "print()" is a debug function and shouldn't be submitted.
repositories/compare_cc_deps_test.bzl:39:9: list-append: Prefer using ".append()" to adding a single element list.
repositories/compare_cc_deps_test.bzl:44:9: list-append: Prefer using ".append()" to adding a single element list.
repositories/compare_cc_deps_test.bzl:47:9: print: "print()" is a debug function and shouldn't be submitted.
repositories/compare_cc_deps_test.bzl:48:9: list-append: Prefer using ".append()" to adding a single element list.
repositories/compare_cc_deps_test.bzl:53:9: list-append: Prefer using ".append()" to adding a single element list.
repositories/gnutls.bzl:12:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/gnutls.bzl:14:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.filegroup" on line 15.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/lua.bzl:1:1: function-docstring: The function "BUILD" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/lua.bzl:1:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/lua.bzl:1:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.cc_library" on line 14.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/nettle.bzl:12:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
repositories/nettle.bzl:14:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.filegroup" on line 15.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/openssl.bzl:22:72: load: Loaded symbol "configure_make_variant" is unused. Please remove it.
To disable the warning, add '@unused' in a comment.
If you want to re-export a symbol, use the following pattern:

    load(..., _configure_make_variant = "configure_make_variant", ...)
    configure_make_variant = _configure_make_variant

repositories/openssl.bzl:24:1: function-docstring: The function "BUILD" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/openssl.bzl:24:1: unnamed-macro: The macro "BUILD" should have a keyword argument called "name".

It is considered a macro because it calls a rule or another macro "native.filegroup" on line 27.

By convention, every public macro needs a "name" argument (even if it doesn't use it).
This is important for tooling and automation.

  * If this function is a helper function that's not supposed to be used outside of this file,
    please make it private (e.g. rename it to "_BUILD").
  * Otherwise, add a "name" argument. If possible, use that name when calling other macros/rules.
repositories/repositories.bzl:16:5: no-effect: Expression result is not used. Docstrings should be the first statements of a file or a function (they may follow comment lines).
repositories/repositories.bzl:57:1: function-docstring: The function "com_github_curl_curl" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/repositories.bzl:265:1: function-docstring: The function "com_github_openssl_openssl" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/repositories.bzl:316:1: function-docstring: The function "io_opentelemetry_cpp" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/repositories.bzl:333:1: function-docstring: The function "com_github_apple_oss_common_crypto" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/repositories.bzl:356:5: function-docstring-args: Argument "**args" is not documented.

If the documentation for the argument exists but is not recognized by Buildifier
make sure it follows the line "Args:" which has the same indentation as the opening """,
and the argument description starts with ":" and indented with at least
one (preferably two) space more than "Args:", for example:

    def aws_sdk_cpp(**args):
        """Function description.

        Args:
          **args: argument description, can be
            multiline with additional indentation.
        """
repositories/repositories.bzl:356:5: function-docstring-header: The docstring for the function "aws_sdk_cpp" should start with a one-line summary.
repositories/repositories.bzl:356:5: function-docstring-return: Return value of "aws_sdk_cpp" is not documented.
repositories/repositories.bzl:379:1: function-docstring: The function "com_github_aws_s2n_tls" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/repositories.bzl:397:1: function-docstring: The function "com_github_aws_sdk" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/repositories.bzl:422:1: function-docstring: The function "com_github_awslabs_aws_c_auth" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/repositories.bzl:442:1: function-docstring: The function "com_github_awslabs_aws_c_cal" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/repositories.bzl:462:1: function-docstring: The function "com_github_awslabs_aws_c_common" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/repositories.bzl:479:1: function-docstring: The function "com_github_awslabs_aws_c_compression" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/repositories.bzl:497:1: function-docstring: The function "com_github_awslabs_aws_c_event_stream" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/repositories.bzl:517:1: function-docstring: The function "com_github_awslabs_aws_c_http" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/repositories.bzl:537:1: function-docstring: The function "com_github_awslabs_aws_c_io" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/repositories.bzl:557:1: function-docstring: The function "com_github_awslabs_aws_c_mqtt" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/repositories.bzl:577:1: function-docstring: The function "com_github_awslabs_aws_c_s3" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/repositories.bzl:596:1: function-docstring: The function "com_github_awslabs_aws_c_sdkutils" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/repositories.bzl:614:1: function-docstring: The function "com_github_awslabs_aws_checksums" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
repositories/repositories.bzl:632:1: function-docstring: The function "com_github_awslabs_aws_crt_cpp" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
status_repository/repo.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
status_repository/repo.bzl:55:9: list-append: Prefer using ".append()" to adding a single element list.
status_repository/repo.bzl:56:9: list-append: Prefer using ".append()" to adding a single element list.
status_repository/repo.bzl:58:9: list-append: Prefer using ".append()" to adding a single element list.
status_repository/repo.bzl:59:9: list-append: Prefer using ".append()" to adding a single element list.
tests/BUILD:29:34: load: Loaded symbol "gen_dot" is unused. Please remove it.
To disable the warning, add '@unused' in a comment.
tests/build_test_test.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
tests/build_test_test.bzl:45:1: no-effect: Expression result is not used. Docstrings should be the first statements of a file or a function (they may follow comment lines).
tests/build_test_test.bzl:64:1: function-docstring: The function "build_test_suite" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
tests/build_test_test.bzl:98:5: no-effect: Expression result is not used. Docstrings should be the first statements of a file or a function (they may follow comment lines).
tests/cc_embed_data_test.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
tests/cc_embed_data_test.bzl:56:1: function-docstring: The function "cc_embed_data_suite" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
tests/cc_embed_data_test.bzl:112:5: unused-variable: Variable "gt" is unused. Please remove it.
tests/css_js_test.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
tests/css_js_test.bzl:33:1: function-docstring: The function "css_class_names_js_suite" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
tests/detex_test.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
tests/detex_test.bzl:49:1: function-docstring: The function "detex_suite" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
tests/fail_test.bzl:3:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
tests/gen_dot_test.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
tests/git_stamp_test.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
tests/latex_ref_test_test.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
tests/latex_ref_test_test.bzl:49:1: function-docstring: The function "latex_ref_test_suite" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
tests/parser_test.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
tests/parser_test.bzl:74:1: function-docstring: The function "parser_suite" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
tests/proto_api_test.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
tests/proto_api_test.bzl:31:1: function-docstring: The function "proto_api_suite" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
tests/role_call_test_test.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
tests/role_call_test_test.bzl:48:1: function-docstring: The function "role_call_test_suite" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
tests/spell_test_test.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
tests/spell_test_test.bzl:48:1: function-docstring: The function "spell_test_suite" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
tests/tex_to_pdf_test.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
tests/tex_to_pdf_test.bzl:64:1: function-docstring: The function "tex_to_pdf_suite" has no docstring.
A docstring is a string literal (not a comment) which should be the first statement of a function body (it may follow comment lines).
text/spelling.bzl:28:1: module-docstring: The file has no module docstring.
A module docstring is a string literal (not a comment) which should be the first statement of a file (it may follow comment lines).
text/spelling.bzl:55:7: list-append: Prefer using ".append()" to adding a single element list.
text/spelling.bzl:56:7: list-append: Prefer using ".append()" to adding a single element list.

bcsgh/bazel_rules

Scheduled build