Skip to content

ci: add Dependabot and auto-merge for hotdata SDK updates#14

Merged
eddietejeda merged 3 commits into
masterfrom
ci/dependabot-automerge
Jun 1, 2026
Merged

ci: add Dependabot and auto-merge for hotdata SDK updates#14
eddietejeda merged 3 commits into
masterfrom
ci/dependabot-automerge

Conversation

@eddietejeda
Copy link
Copy Markdown
Contributor

@eddietejeda eddietejeda commented Jun 1, 2026

Adds daily Dependabot checks scoped to hotdata and hotdata-runtime packages, and an auto-merge workflow that squash-merges those PRs once all checks pass.

  • dependabot.yml: watches the correct package ecosystem (uv where uv sync --locked is used in CI, pip otherwise), scoped via allow: to hotdata packages only
  • dependabot-automerge.yml: enables squash auto-merge on any PR opened by dependabot[bot]

Comment thread .github/dependabot.yml
Copy link
Copy Markdown

@claude claude Bot left a comment

Choose a reason for hiding this comment

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

Review

Blocking Issues

  • .github/dependabot.yml: PR title and description claim "Dependabot and auto-merge for hotdata SDK updates," but the diff only adds a generic pip Dependabot config. There is no auto-merge workflow, and the config is not scoped to hotdata packages — it will open daily PRs for marimo, pytest, hotdata-runtime, and hotdata alike.

Action Required

Pick one:

  1. Land what the description promises in this PR — add an allow filter (and probably labels) so Dependabot only opens PRs for hotdata / hotdata-runtime, and add a workflow that calls gh pr merge --auto --squash on Dependabot PRs targeting those packages once checks pass.
  2. Narrow the PR description to match the diff — "adds daily Dependabot for pip dependencies" — and follow up with the auto-merge workflow in a separate PR.

Either is fine; the current mismatch between description and code shouldn't merge as-is.

@eddietejeda eddietejeda merged commit c4c1a1c into master Jun 1, 2026
2 checks passed
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