Skip to content

ci: add workflow to check lib-sync#1230

Open
klaskosk wants to merge 2 commits intorh-ecosystem-edge:mainfrom
klaskosk:sync-checker-action
Open

ci: add workflow to check lib-sync#1230
klaskosk wants to merge 2 commits intorh-ecosystem-edge:mainfrom
klaskosk:sync-checker-action

Conversation

@klaskosk
Copy link
Collaborator

@klaskosk klaskosk commented Jan 16, 2026

It is possible for the sync-libs automation to break if changes are made to sync configs or schemes that have not been verified to work with automation. This commit introduces a new workflow that runs specifically on PRs updating these paths and ensures that running make lib-sync against the PR does not introduce any errors.

Assisted-by: Cursor

Summary by CodeRabbit

  • Chores
    • Added an automated CI check that verifies dependency sync and code vetting on pull requests to main and release branches; also supports manual runs.

✏️ Tip: You can customize this high-level summary in your review settings.

It is possible for the sync-libs automation to break if changes are made
to sync configs or schemes that have not been verified to work with
automation. This commit introduces a new workflow that runs specifically
on PRs updating these paths and ensures that running `make lib-sync`
against the PR does not introduce any errors.

Assisted-by: Cursor
@coderabbitai
Copy link

coderabbitai bot commented Jan 16, 2026

📝 Walkthrough

Walkthrough

Adds a GitHub Actions workflow that verifies lib-sync is up to date on pull requests to main and release-* branches and supports manual dispatch; it checks out the repo, sets Go from go.mod, runs the lib-sync target, and validates the vet step.

Changes

Cohort / File(s) Summary
CI/CD Workflow Configuration
/.github/workflows/sync-checker.yml
New workflow (34 lines added) that triggers on pull requests to main and release-* and manual dispatch. Job checks out code, sets up Go using go.mod, runs the lib-sync target, and runs vet validation.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'ci: add workflow to check lib-sync' directly and clearly describes the main change: adding a CI workflow for checking lib-sync, which matches the changeset that adds a GitHub Actions workflow.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@klaskosk
Copy link
Collaborator Author

@klaskosk klaskosk force-pushed the sync-checker-action branch from 072f0b0 to e0c7e27 Compare January 16, 2026 21:19
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In @.github/workflows/sync-checker.yml:
- Around line 5-7: The branches filter is using a regex-like string
'release-\d.\d\d' which GitHub Actions does not support; update the branches
array entry to a glob pattern such as 'release-[0-9].[0-9][0-9]' (or another
appropriate glob like 'release-*' if broader matching is acceptable) so the
workflow will trigger for release branches; modify the branches list entry that
currently contains 'release-\d.\d\d' to the chosen glob pattern.

Sign up for free to 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.

1 participant