Keep your changelog updated automatically
Maintaining a changelog manually means constantly switching between GitHub and Linear. Let Notis automatically add commit details to your changelog issue so release notes stay current without extra work.
Trigger
Commit Event
Triggered when a new commit is pushed to a repository.
Action
Create a comment
Creates a new comment on a specified linear issue.
Why this helps
Changelog maintenance is boring but important. Forgetting to capture commits as they land means changelog updates become a tedious catch-up task. Neurodivergent founders often skip tedious administrative work, leaving changelogs stale until someone finally syncs them manually.
- Changelog stays current automatically without manual updates
- No need to hunt through GitHub commits when shipping
- Release notes are ready when you need them
- Reduce tedious administrative work
Setup
Build it in a few focused steps.
- 1Connect GitHub and Linear to Notis.
- 2Create the automation: 'When a commit is pushed to main, add the commit message to my changelog Linear issue.'
- 3Select your notification channel.
- 4Choose the trigger: Commit Event (filtered for main branch).
- 5Test by committing to main and verify the changelog Linear issue gets updated.
Questions about this workflow
Can I filter by commit author or message content?
Yes. Your prompt can specify patterns like 'only include commits with feature or fix prefixes' to keep the changelog focused.
What if I make many small commits?
You can configure Notis to group commits by hour or day, or include all of them separately. It's your choice.
How do I handle release branches separately from main?
Notis can create separate changelog issues per branch or filter to only track specific branches in your prompt.
Can I include commit authors in the changelog?
Yes. Notis automatically includes author names, timestamps, and commit links in the changelog updates.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Linear. A trigger fires from one place; an action lands in another.
GitHub triggers
Linear 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.
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
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.
Create a comment
Creates a new comment on a specified linear issue.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create linear issue
Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.
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 create issue default params
Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
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 a label
Creates a new label in linear for a specified team, used to categorize and organize issues.
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.
Delete issue
Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
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 all teams
Retrieves all teams from the linear workspace without requiring any parameters.
Commit Event
Triggered when a new commit is pushed to a repository.
Download issue attachments
Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.
Connect any two apps with Notis in the middle.
Not just GitHub and Linear. Any combination from 985+ 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 Linear.