Chuck Grindel
Chuck Grindel
The problem is that we do not want to add it to the `cxxopts` for each target. It would override the values in the .bazelrc. Also, I think that you...
- Ensure that the `Gen` and `Empty` attributes are specified properly. - Perhaps create an equivalent to `gazelle_generation_test` for `update-repos` or modify it to support this kind of test.
## Tasks - [ ] Add `bzlmod` support to `swift_bazel` deps: - [ ] `cgrindel/bazel-starlib` - [ ] `bazel-contrib/rules_bazel_integration_test` - [ ] Implement `bzlmod` support for `swift_bazel`
Right now, the code checks the PATH for a Swift binary. We should be using the Swift toolchain binary as defined in a repository's Bazel workspace.
Example: `@apple_swift_argument_parser//Plugins/GenerateManualPlugin:Generate Manual` The above should be `@apple_swift_argument_parser//Plugins/GenerateManualPlugin:Generate_Manual`
https://swiftpackageregistry.com/about
Goals - Highlight the `feat:` and `fix:` entries at the beginning of the release notes. - List the `chore:` and `fix(deps):` at the end.
Some generated code was added. I believe that I need to remove [the `--to_macro` line](https://github.com/cgrindel/bazel-starlib/blob/main/BUILD.bazel#L34) Also, add the `WORKSPACE.bzlmod` [per fmeum comment](https://bazelbuild.slack.com/archives/C01HMGN77Q8/p1690473505823769?thread_ts=1690470169.636879&cid=C01HMGN77Q8).
[Query for related PRs](https://github.com/cgrindel/bazel-starlib/pulls?q=is%3Apr++kingpin) This PR can never succeed. `kingpin` changed their path in a version later than is needed for the `github-markdown-toc.go`. Also, it sounds like `kingpin` is in...