Repository navigation
ci: add GitHub Actions workflows and repo CI configuration - #2
Merged
Merged
Conversation
Port the relevant CI subset from kai-scheduler/KAI-Scheduler: - on-pr: validate+test jobs only (no Docker/e2e/Helm) - release-prepare + release-publish: changie-based release flow - validate-pr-title, validate-changelog, dco, approval-gatekeeper - coverage tracking (gate, badge, PR comment), backport, changelog-comment - dependabot for GitHub Actions + Go modules (main only, k8s grouping) - .golangci.yaml, .changie.yaml, .coderabbit.yaml, PR/issue templates Signed-off-by: SiorMeir <msior@nvidia.com>
SiorMeir
force-pushed
the
siormeir/export-actions
branch
from
July 16, 2026 10:44
23eac53 to
73da9e3
Compare
- Import .github/scripts/dco_check.py (required by dco.yaml) - Add -coverprofile to make test so coverage artifact is produced Signed-off-by: SiorMeir <msior@nvidia.com>
…association author_association returns CONTRIBUTOR instead of MEMBER on new repos, causing org members to be treated as external contributors. Check repo permission level directly via the API instead. Signed-off-by: SiorMeir <msior@nvidia.com>
update-coverage-badge.yaml doesn't exist on main yet, so the baseline lookup fails with 404. continue-on-error lets the PR pass; self-heals after the first merge to main runs the badge workflow. Signed-off-by: SiorMeir <msior@nvidia.com>
gshaibi
approved these changes
Jul 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Ports the relevant CI subset from
kai-scheduler/KAI-Schedulerto this standalone API module repo. The scheduler's CI is heavy (Docker builds, Helm, e2e on Kind clusters); this PR brings only what makes sense for a pure Go module.Workflows added (verbatim from KAI-Scheduler):
on-pr— trimmed tovalidate-and-test+code-coverage-reportonly; no Docker/e2e/Helm jobsrelease-prepare+release-publish— changie fragment → CHANGELOG fold → tag + GitHub Releasevalidate-pr-title,validate-changelog,dco,approval-gatekeepercoverage-gate,update-coverage-badge,post-coverage-commentbackport,changelog-commentConfig files added:
dependabot.yml— GitHub Actions + Go modules weekly (main only, k8s grouping; backport branches stripped until they exist).golangci.yaml,.changie.yaml,.coderabbit.yaml.github/pull_request_template.md,.github/ISSUE_TEMPLATE/.changes/header.tpl.mdDropped from scheduler (not applicable here):
benchmark*,on-release,push-artifacts,deploy-scale-tests-page,stale,.fossa.ymlRelated Issues
N/A
Checklist
skip-changeloglabel (CI-only change, no behavior change)Breaking Changes
None — first CI setup for this repo.
Additional Notes
After this merges, the dev needs to:
KAIBOT_TOKENsecret to the repo (used byrelease-prepareandrelease-publish)