Skip to content

Add one-command Kaggle pre-upload release gate - #13

Merged
karlwaldman merged 1 commit into
masterfrom
codex/issues-5-6-kaggle-practices
Jul 25, 2026
Merged

karlwaldman merged 1 commit into
masterfrom
codex/issues-5-6-kaggle-practices

Conversation

@karlwaldman

Copy link
Copy Markdown
Member

Summary

  • add a one-command pre-upload gate that regenerates notebooks, rejects drift, scans secrets, validates JSON, executes exact cells against production-shaped fixtures, and builds Kaggle CLI packages
  • align CI with the documented Python SDK 1.11.0 pin and run the same operator gate used locally
  • document deterministic notebook authoring, Kaggle Secrets, failure recovery, package/publish/status steps, public-output review, and honest distribution/SEO rules

Verification

  • clean Python virtual environment
  • ./scripts/validate_before_upload.sh
  • 5 notebook contract tests pass; both exact notebooks execute against fixtures
  • secret scan and deterministic regeneration pass
  • both public Kaggle packages build
  • git diff --check

No Kaggle kernel was published or updated by this PR.

Closes #5
Closes #6

@coderabbitai

coderabbitai Bot commented Jul 25, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@karlwaldman, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 36 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e17fec02-4096-4c4e-a06a-a0500f7f39a7

📥 Commits

Reviewing files that changed from the base of the PR and between ec45c03 and db81ef2.

📒 Files selected for processing (4)
  • .github/workflows/validate.yml
  • KAGGLE_BEST_PRACTICES.md
  • README.md
  • scripts/validate_before_upload.sh
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/issues-5-6-kaggle-practices

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.

@karlwaldman
karlwaldman merged commit 2e7dde0 into master Jul 25, 2026
2 checks passed
@karlwaldman
karlwaldman deleted the codex/issues-5-6-kaggle-practices branch July 25, 2026 18:49
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.

🔵 P3: Document Kaggle notebook best practices 🟡 P2: Improve local notebook testing to avoid Kaggle upload failures

1 participant