See How Your Code Patterns Spread
You share a useful code pattern in Gist, and developers fork it for their own needs. Notis tracks all forks so you see how your patterns are adapted and can share improvements back.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
List Gist Forks
Tool to list forks of a gist. Use after obtaining a gist_id to retrieve all forks for the gist.
Why this helps
Developers fork useful Gists to adapt them for their own projects, but you never know about the variants. Good improvements made in forks never make it back to the original.
- See how patterns are being used
- Identify improvements made in forks
- Prevent divergence in core patterns
- Share lessons across variants
Setup
Build it in a few focused steps.
- 1Connect Gist to Notis and identify your template or shared Gists
- 2Create an automation called 'Gist Fork Tracking'
- 3In the Prompt, write: 'When a Monday task mentions adapting, forking, or creating a variant of a Gist, list all forks of that Gist to see how the pattern is being used'
- 4Set Trigger to webhook, choose your notification channel, and save
- 5Test by creating a Monday task that mentions forking a shared Gist
Questions about this workflow
Can it track private forks?
Notis can list public forks. For private forks, team members would need to tag the Monday task with fork references so Notis knows to track them.
Can it suggest sharing improvements back?
Yes. Notis can review forks and suggest valuable changes that should be merged back into the original, keeping patterns in sync.
What if developers fork and stop maintaining them?
Notis will show you all forks. You can use that data to decide if a fork should be retired or merged back into the mainline.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Monday to Gist. A trigger fires from one place; an action lands in another.
Monday triggers
Gist actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Gist Star
Tool to check if a gist is starred. Use when you need to determine if the authenticated user has starred a specific gist.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Gist Comment
Tool to delete a comment on a gist. Use when you have both the gist_id and comment_id and want to remove that comment. Example prompt: "Delete comment 42 from gist 'aa5a315d61ae9438b18d'".
Get Gist
Tool to retrieve a specific gist by its ID. Use when you have a gist_id and need complete gist details.
Get Gist Comment
Tool to get a specific comment on a gist. Use when you need to retrieve details of a particular comment given gist_id and comment_id.
Get Gist Revision
Tool to retrieve a specific gist revision. Use when you need details of a past state for an existing gist by commit SHA.
List Gist Comments
Tool to list comments on a gist. Use after confirming the gist_id to retrieve comments for a specific gist. Example: 'List comments for gist abc123'.
List Gist Commits
Tool to list the commit history of a gist. Use after you have the gist ID to review its revisions.
List Gist Forks
Tool to list forks of a gist. Use after obtaining a gist_id to retrieve all forks for the gist.
Connect any two apps with Notis in the middle.
Monday and Gist, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Gist.