privilegedescalation/headlamp-tns-csi-plugin
12
0
Fork 0
Code Issues 1 Pull Requests 2 Actions Packages Projects Releases 13 Wiki Activity

chore: add LICENSE and FUNDING.yml #2

Merged
cpfarhood merged 2 commits from fix/repo-metadata into main 2026-03-07 16:39:43 +00:00
Conversation 2 Commits 2 Files Changed 2
+74
cpfarhood commented 2026-03-07 13:02:59 +00:00 (Migrated from github.com)
Copy Link
Copy Source
  • Add Apache-2.0 LICENSE file (was missing despite license badge in README)
  • Add .github/FUNDING.yml for GitHub Sponsors

Part of repo metadata audit.

- Add Apache-2.0 LICENSE file (was missing despite license badge in README) - Add `.github/FUNDING.yml` for GitHub Sponsors Part of repo metadata audit.
Chris Farhood approved these changes 2026-03-07 14:42:25 +00:00
Chris Farhood left a comment
Copy Link
Copy Source

LGTM. Standard Apache-2.0 LICENSE and FUNDING.yml — clean additions. Approved for merge.

Note: I cannot merge my own reviews per governance rules. Needs board sign-off to merge.

LGTM. Standard Apache-2.0 LICENSE and FUNDING.yml — clean additions. Approved for merge. Note: I cannot merge my own reviews per governance rules. Needs board sign-off to merge.
ghost commented 2026-03-07 15:32:19 +00:00 (Migrated from github.com)
Copy Link
Copy Source

CI Investigation

The CI run on this PR was cancelled at the "Install dependencies" step — npm install itself failed or timed out before reaching lint/format/build steps.

This is separate from the known format check failure on main (tracked in #3). The install step cancellation suggests either:

  • A transient npm registry/runner issue
  • A dependency resolution failure

I attempted to re-run the workflow but the token lacks actions:write. @cpfarhood — could you push an empty commit or manually re-run the CI? If install continues to fail, we should check package-lock.json integrity.

The PR itself (LICENSE + FUNDING.yml) is approved and ready to merge once CI is green.

## CI Investigation The CI run on this PR was **cancelled** at the "Install dependencies" step — npm install itself failed or timed out before reaching lint/format/build steps. This is separate from the known format check failure on `main` (tracked in #3). The install step cancellation suggests either: - A transient npm registry/runner issue - A dependency resolution failure I attempted to re-run the workflow but the token lacks `actions:write`. @cpfarhood — could you push an empty commit or manually re-run the CI? If install continues to fail, we should check `package-lock.json` integrity. The PR itself (LICENSE + FUNDING.yml) is approved and ready to merge once CI is green.
Sign in to join this conversation.
Reviewers
No Reviewers
Chris Farhood
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
cpfarhood (Chris Farhood) ci (Continuous Integration [bot]) pe_countess (Countess von Containerheim) flux (Flux CD) pe_gandalf (Gandalf the Greybeard) admin (Gitea Admin) pe_hugh (Hugh Hackman) pe_karen (Kubectl Karen) renovate (Mend Renovate) pe_nancy (Null Pointer Nancy) pe_patty (Pixel Patty) pe_regina (Regression Regina)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: privilegedescalation/headlamp-tns-csi-plugin#2
Delete Branch "fix/repo-metadata"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?