<feed xmlns='http://www.w3.org/2005/Atom'>
<title>tazelish/.github/workflows, branch main</title>
<subtitle>Installs Tazel and chooses which version of it runs.</subtitle>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazelish/'/>
<entry>
<title>Pin the CodeQL action to v4.39.3 with its version</title>
<updated>2026-11-05T04:09:44+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-05T04:09:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazelish/commit/?id=81dc32cf25a8efe117eff48d3ce832ffbf57068a'/>
<id>81dc32cf25a8efe117eff48d3ce832ffbf57068a</id>
<content type='text'>
zizmor found that the pinned commit was not the one the v4 comment
named; the pin is the commit of v4.39.3 and says so.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
zizmor found that the pinned commit was not the one the v4 comment
named; the pin is the commit of v4.39.3 and says so.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Give the coverage job llvm-profdata under the name rules_cc reads</title>
<updated>2026-11-05T04:08:30+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-05T04:08:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazelish/commit/?id=307aa5e8825c7b087d3257a8ed80dc508e3f475e'/>
<id>307aa5e8825c7b087d3257a8ed80dc508e3f475e</id>
<content type='text'>
rules_cc takes llvm-profdata from BAZEL_LLVM_PROFDATA; GCOV left the
coverage script without it.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
rules_cc takes llvm-profdata from BAZEL_LLVM_PROFDATA; GCOV left the
coverage script without it.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Add CodeQL, Codecov, Codacy, Renovate and actionlint</title>
<updated>2026-11-05T04:00:01+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-05T04:00:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazelish/commit/?id=77a86bbd91a603e04fb64338a31d1bd8e9a13b22'/>
<id>77a86bbd91a603e04fb64338a31d1bd8e9a13b22</id>
<content type='text'>
- CodeQL analyses the workflows and the C++ sources, without a build,
  with the security-extended queries, on every push to main, every pull
  request and once a week.
- A coverage job runs the tests under Clang's own coverage on Linux and
  a job of its own uploads the lcov report to Codecov through OIDC.
- .codacy.yml leaves out the output of Bazel and the rules_cc patch.
- Renovate proposes Bazel modules, Bazel itself and GitHub Actions once
  a week, a week after their release; rules_cc waits for approval on
  the dashboard, since its clang-cl patch has to be checked first.
- actionlint joins zizmor in Workflow Security.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
- CodeQL analyses the workflows and the C++ sources, without a build,
  with the security-extended queries, on every push to main, every pull
  request and once a week.
- A coverage job runs the tests under Clang's own coverage on Linux and
  a job of its own uploads the lcov report to Codecov through OIDC.
- .codacy.yml leaves out the output of Bazel and the rules_cc patch.
- Renovate proposes Bazel modules, Bazel itself and GitHub Actions once
  a week, a week after their release; rules_cc waits for approval on
  the dashboard, since its clang-cl patch has to be checked first.
- actionlint joins zizmor in Workflow Security.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Start Tazelish with its command line and version files</title>
<updated>2026-11-05T03:29:20+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-05T03:29:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazelish/commit/?id=52490ff852f3d72ce9c9eb76898080223e9e17fd'/>
<id>52490ff852f3d72ce9c9eb76898080223e9e17fd</id>
<content type='text'>
Tazelish installs Tazel and chooses which version of it runs, for those
who use Tazel alone. This first part holds everything that needs no
download:

- Versions: MAJOR.SEMIMAJOR.MINOR.PATCH without leading zeros,
  unstable, nightly, and YYYY-MM-DD-unstable or -nightly with a date
  the calendar has.
- The command line, read by hand into a typed command: install, use
  and default with --force before or after the version, self
  update|remove|purge, and help with or without a command. A wrong
  command line ends with exit code 2.
- tazelish.txt and config.txt: the nearest tazelish.txt in the current
  folder or above it comes first, then $HOME/.tazelish/config.txt or
  %USERPROFILE%\.tazelish\config.txt. use and default refuse to write
  over a file that exists unless --force is given.

install and self download from static.tazel.net, which this build does
not do; they say so and end with exit code 1.

C++17 with fmt, tested with Catch3, built by Bazel (clang-cl on
Windows, with the rules_cc patch the Tala repository carries). The code
throws no exceptions and builds with warnings as errors; the tests
leave out -Wconversion, which the headers of Catch3 do not pass. CI
tests on Linux, macOS and Windows.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Tazelish installs Tazel and chooses which version of it runs, for those
who use Tazel alone. This first part holds everything that needs no
download:

- Versions: MAJOR.SEMIMAJOR.MINOR.PATCH without leading zeros,
  unstable, nightly, and YYYY-MM-DD-unstable or -nightly with a date
  the calendar has.
- The command line, read by hand into a typed command: install, use
  and default with --force before or after the version, self
  update|remove|purge, and help with or without a command. A wrong
  command line ends with exit code 2.
- tazelish.txt and config.txt: the nearest tazelish.txt in the current
  folder or above it comes first, then $HOME/.tazelish/config.txt or
  %USERPROFILE%\.tazelish\config.txt. use and default refuse to write
  over a file that exists unless --force is given.

install and self download from static.tazel.net, which this build does
not do; they say so and end with exit code 1.

C++17 with fmt, tested with Catch3, built by Bazel (clang-cl on
Windows, with the rules_cc patch the Tala repository carries). The code
throws no exceptions and builds with warnings as errors; the tests
leave out -Wconversion, which the headers of Catch3 do not pass. CI
tests on Linux, macOS and Windows.
</pre>
</div>
</content>
</entry>
</feed>
