NVIDIA / nodewright / 36788482061
83%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 59
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: 82.201% (+0.06%) from 82.14%
36788482061

push

github

web-flow 
chore: add NOTICE, release checksums and read-only workflow tokens (#720)

* docs: add a root NOTICE and link the published docs from the README

The repository had no NOTICE at its root, only THIRD_PARTY_NOTICES.md,
and the README never pointed at the published documentation at
docs.nvidia.com/nodewright, which fern/docs.yml publishes docs/ to.

Add a plain-text Apache-2.0 NOTICE naming the project, its copyright
holder and first-publication year, its license, and where third-party
licenses are listed. Link the hosted docs next to the README sentence
that points at docs/.

Signed-off-by: Alex Yuskauskas <ayuskauskas@nvidia.com>

* docs: explain how issue priority is set and how to question it

Priority lives in the native GitHub Priority issue field, set by
maintainers during triage, but only .github/labels.yml and the agent
instructions said so. Contributors had no way to learn that priority is
never a label, what raises it, or how to ask for it to change.

Add an "Issue priority" subsection under Filing Issues that states the
existing practice: the field and its four values, that it is not a label
and not set by reporters, the one factor SUPPORT.md already documents,
and that a contributor who disagrees comments on the issue with context
for a maintainer to decide.

Signed-off-by: Alex Yuskauskas <ayuskauskas@nvidia.com>

* ci: attach a verified checksums.txt to operator, agent and chart releases

release.yml uploaded only the component's THIRD_PARTY_NOTICES file, so
operator, agent and chart releases carried no checksums, while CLI
releases already attach checksums.txt through cli-release.yaml.

The upload step now copies the notices file it already selects for the
tag's component into a fresh directory under its asset name, writes
checksums.txt there in the CLI's format (sha256sum output keyed by asset
name), verifies it with sha256sum -c, and uploads both files from that
directory in one --clobber call. The file is staged rather than hashed
in p... (continued)

9486 of 11540 relevant lines covered (82.2%)

7.62 hits per line

Coverage Regressions

Lines Coverage ∆ File
8
79.15
-0.27% operator/internal/controller/skyhook_controller.go
Jobs
ID Job ID Ran Files Coverage
1 36788482061.1 59
82.2
GitHub Action Run
Source Files on build 36788482061