Skip to content

chore(sdk/go): remove coverage.out from tracking - #2774

Merged
elezar merged 1 commit into
NVIDIA:mainfrom
rhuss:chore/remove-coverage-out
Aug 18, 2026
Merged

chore(sdk/go): remove coverage.out from tracking#2774
elezar merged 1 commit into
NVIDIA:mainfrom
rhuss:chore/remove-coverage-out

Conversation

@rhuss

Copy link
Copy Markdown
Contributor

Summary

  • Remove sdk/go/coverage.out from git tracking. This is a go test -coverprofile artifact that was accidentally committed and should not be in the repo. Already covered by .gitignore line 67.

Related Issue

No issue required. Mechanical cleanup of an accidentally committed test artifact.

Changes

  • git rm --cached sdk/go/coverage.out

Testing

  • git ls-files sdk/go/coverage.out returns empty after this change
  • .gitignore already has coverage.out at line 67, preventing future commits

Checklist

  • Change is mechanical (file removal only)
  • No code changes
  • No issue required

Test coverage artifact was accidentally committed. Already in .gitignore.
Signed-off-by: Roland Huß <rhuss@redhat.com>
@copy-pr-bot

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@rhuss

Copy link
Copy Markdown
ContributorAuthor

@krishicks this file slipped in with 7547edc (although its in the top-level .gitignore). Quick PR to remove it again.

@rhuss

Copy link
Copy Markdown
ContributorAuthor

Thanks to @grs for pointing this out.

@elezar
elezar enabled auto-merge August 17, 2026 13:25
@elezar

Copy link
Copy Markdown
Member

/ok-to-test fda8624

@elezar
elezar added this pull request to the merge queueAug 18, 2026
Merged via the queue into NVIDIA:main with commit dc374e8Aug 18, 2026
50 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@rhuss@elezar