Keep Pull Request Milestones Visible
Make important delivery movement visible without checking every repository.
Trigger
Pull Request Event
Triggered when a pull request is opened, closed, or synchronized.
Action
Create a new Fireberry record
Tool to create a new record in a specified fireberry table. use when you have the table name and record data ready for insertion.
Why this helps
A merged or reopened pull request can change a customer commitment, but the founder may not notice the event until much later.
- Creates a record when a monitored pull request changes state.
- Makes merged, closed, or synchronized work easier to connect to commitments.
- Reduces manual status updates after code movement.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Fireberry to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create a Fireberry record for each relevant pull request event.
- 3Use a plain-language instruction to summarize the event, pull request, repository, commit context, and next business step.
- 4Choose the pull request event trigger, select the reporting channel, and test with one real event.
Questions about this workflow
Which pull request events are covered?
The trigger covers pull requests that are opened, closed, or synchronized.
Can the instruction focus on merged work?
Yes. Ask Notis to emphasize merged or closed outcomes in the record.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Fireberry. A trigger fires from one place; an action lands in another.
GitHub triggers
Fireberry 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 a new Fireberry record
Tool to create a new record in a specified fireberry table. use when you have the table name and record data ready for insertion.
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.
Get Picklist Values
Tool to retrieve all possible picklist (dropdown) values for a specific field. use when you need to load all available options for a picklist field in a record type.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Fireberry: Query Records
Tool to query records with filtering, sorting, and pagination. use when you need to retrieve specific fireberry records by module.
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.
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.
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.
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.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Fireberry. 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 Fireberry.