Tatsh / kate-wakatime / 33332894958
100%

DEFAULT BRANCH: master
Ran
Jobs 1
Files 3
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 100.0%. Remained the same
33332894958

push

github

Tatsh 
cruft: update

Regenerate with Wiswa deaad5b, then repair the project-specific content
the generator overwrote and harden the hand-written workflows.

Generator changes kept: Dependabot cooldown, zizmor pre-commit hook and
config, clang-format InsertBraces, LC_ALL=C dictionary sorting, Yarn
4.18.0, cspell 10.1.0, publish-winget workflow, make-release skill
replacing the release agent, comments rule, pre-commit.ci badge.

Restored what the regen replaced with Python-project scaffolding:

- tests.yml had become a uv/pytest matrix. Restored the CMake build,
  ctest run, install-prefix artifact, geninfo coverage, and Coveralls
  upload, along with the C/C++ path filters.
- codeql.yml lost the KDE Neon dependency install, fetch-depth, the
  autoinstall opt-out, the Autobuild step, and the actions language.
  Without Autobuild the C++ database is never built.
- Dropped the zizmor ignore for pyinstaller.yml, which does not exist
  here, and sorted the stray .sbclaude-venv gitignore entry.

The ecm constraint in vcpkg.json had been rolled back from 6.29.0 to
6.25.0. That is the literal in .wiswa.jsonnet, so every regen undid the
bump Dependabot had already landed. Resolve it with the generator's
latestVcpkgPortVersion instead, which reads the vcpkg version database
and currently yields the 6.29.0 already in vcpkg.json.

Hand-written workflows (cmake, pages, publish-msys2, qa, release) now
match the generated ones: every action pinned to a full-length commit
SHA, checkouts no longer persist credentials, and step outputs are
passed through env instead of being interpolated into run blocks.
zizmor reports no findings across all twelve workflows.

Release publishing is stricter. Build is now a required workflow, so a
tag whose build never ran, was skipped, or failed can no longer be
un-drafted; previously a missing run was treated as optional. Publishing
verifies the release exists and is still a draft before editing it and
that it is no longer a draft afterwards... (continued)

141 of 141 relevant lines covered (100.0%)

6.84 hits per line

Jobs
ID Job ID Ran Files Coverage
1 33332894958.1 3
100.0
 GitHub Action Run
Source Files on build 33332894958