Read-only mirrors. Development, issues and pull requests are on GitHub.

summaryrefslogtreecommitdiffhomepage
path: root/tests/SelfTest/UsageTests/ToStringVector.tests.cpp
diff options
context:
space:
mode:
authorLeitwolf112026-11-15 23:08:05 +0300
committerLeitwolf112026-11-15 23:08:05 +0300
commit67c3ef401b34716f7214374ff0d6c24b3c50a149 (patch)
treec4c97fb09f6e1364d8b44f74fca32f18065588b0 /tests/SelfTest/UsageTests/ToStringVector.tests.cpp
parent2fbb5585e35078cb2490c8ae988860aa6dc0399d (diff)
downloadcatch3-67c3ef401b34716f7214374ff0d6c24b3c50a149.tar.gz
Prepare the Bazel Central Registry entry as progmasoft_catch3
- MODULE.bazel names the module progmasoft_catch3, the name it has in the registry, with bazel_compatibility >=8.0.0; //tools:version finds the version under the new name. - .bcr/ holds the templates publish-to-bcr fills: metadata, source (the GitHub archive of the catch3-* tag) and the presubmit, which runs the test module on Debian, Ubuntu, macOS (x86-64 and arm64) and Windows with Bazel 8.x and 9.x. - tests/Progmasoft/BazelModule is a module that depends on Catch3 as a user's does, through //:catch3_main and through //:catch3 with its own main. The root ignores it; Bazel Builds tests it with Bazel 8.x and 9.x on Ubuntu and Windows. - Publish to BCR runs when a catch3-* release is published, or by hand for a tag, and opens the registry pull request from the fork of the maintainer, without attestations. - The integration guide says how a module depends on progmasoft_catch3. Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
Diffstat (limited to 'tests/SelfTest/UsageTests/ToStringVector.tests.cpp')
0 files changed, 0 insertions, 0 deletions