Make tagged releases reproducible
A GitHub tag can automatically mark the next Kaggle dataset version, keeping code and data releases aligned.
Trigger
New Repository Tag Created
Triggers when a new tag is created in a GitHub repository. Monitors the repository's tags and fires an event for each newly created tag. The payload includes the tag name, the commit SHA and URL it points to, and archive download URLs.
Action
Create Dataset Version
Tool to create a new dataset version on Kaggle. Use when you have updated files or metadata and need to publish a new version of an existing dataset.
Why this helps
Code releases and dataset versions drift apart when publishing data is a separate manual chore.
- Align code and data releases
- Improve experiment traceability
- Remove a repetitive release step
Setup
Build it in a few focused steps.
- 1Connect GitHub and Kaggle to Notis once through the portal.
- 2Create an automation and tell Notis: When a new GitHub repository tag is created, create a new version of the matching Kaggle dataset and report the version details.
- 3Select the new repository tag trigger and choose the channel for run reports.
- 4Test it with a pre-release tag.
Questions about this workflow
Why use a tag as the trigger?
Tags provide a clear release point that can be associated with a stable dataset version.
What if the dataset files have not changed?
Notis can report that no new version was needed or proceed according to the instruction you provide.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Kaggle. A trigger fires from one place; an action lands in another.
GitHub triggers
Kaggle actions
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Download competition data files
Tool to download competition data files. Use after confirming the competition ID.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Initialize Kaggle Configuration
Tool to initialize Kaggle API client configuration. Attempts CLI first; if unavailable, it falls back to creating ~/.kaggle/kaggle.json (or $KAGGLE_CONFIG_DIR/kaggle.json).
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Dataset Create
Tool to create a new Kaggle dataset with full metadata. Use after uploading files and finalizing metadata. Returns creation status and message.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Get Dataset Status
Tool to get the status of a dataset upload or processing job. Use after uploading a dataset to check processing state.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Create Dataset Version
Tool to create a new dataset version on Kaggle. Use when you have updated files or metadata and need to publish a new version of an existing dataset.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Submit Competition Entry
Tool to submit an entry to a Kaggle competition. Use when you have already uploaded your file and obtained its blob token.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Get Kaggle Config Directory
Tool to retrieve the directory of the Kaggle API configuration file. Use when you need to locate the directory containing your kaggle.json credentials.
Commit Event
Triggered when a new commit is pushed to a repository.
Get Kaggle Config File
Tool to retrieve the filename of the Kaggle API configuration file. Use when you need to find out where the local Kaggle config file is stored before reading or updating.
Connect any two apps with Notis in the middle.
Not just GitHub and Kaggle. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Kaggle.