n8n
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
- 212k
- TypeScript
- 28 min ago
๐ The heartbeat and automation hub powering the @openapiยฎ open-source ecosystem.
Repo openapi/pulse, read from GitHub 4 min ago. openapi has not joined Take My Repo.
openapi/pulse is a public repo on GitHub by openapi. ๐ The heartbeat and automation hub powering the @openapiยฎ open-source ecosystem. It declares the MIT license on GitHub. It is written mainly in Python, has 13 stars and last changed on 2026-11-16. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-22.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
The heartbeat of the Openapi open-source ecosystem.
Pulse is the coordination and automation hub behind the continuous activity of the Openapi GitHub ecosystem.
Open-source ecosystems grow through consistency.
Repositories need to be maintained, releases need to happen, projects need to be highlighted, examples need to be published, contributors need attention, and the overall ecosystem needs a visible and predictable rhythm.
Pulse exists to coordinate that rhythm from a single place.
Pulse orchestrates recurring activities across the Openapi GitHub organization.
It can coordinate things such as:
The goal is not simply to automate tasks.
The goal is to make sure that the Openapi open-source ecosystem never stops moving.
Pulse introduces a regular heartbeat into the organization.
Each cycle can select one or more repositories and trigger coordinated activities around them.
For example:
OPENAPI PULSE
โ
โโโโโโโโโโโโผโโโโโโโโโโโ
โ โ โ
Weekly Monthly Events
Pulse Pulse Pulse
โ
โ
Select Repository
โ
โโโโโโโโผโโโโโโโโโ
โ โ โ
Release Improve Promote
โ โ โ
โโโโโโโโผโโโโโโโโโ
โ
Measure
โ
โ
Next Pulse
Pulse turns isolated maintenance activities into a continuous process.
The Pulse Card is the component the Pulse engine distributes: a single SVG, embedded once near the top of every repository README in the organization, that acts as a weekly news ticker for the ecosystem and routes readers to a single call to action โ the Discussions.
The card above is live. This is the prototype currently in public/.
It carries four tracks: the API of the week, the Developer of the week and the Contributor of the week โ both with their GitHub avatar โ and the Community discussion worth joining.
The content lives in exactly one place. Repositories embed a stable URL and never need an editorial commit again โ the update happens only here.
content/current.yml โ the CTA, the people queues
content/apis.yml โ the API queue
content/topics.yml โ the discussion queue
content/blog.yml โ the blog relay queues
โ
generator/sync.py โ refreshes the queues from their sources
generator/build.py โ renders both themes, embeds the avatars
generator/publish.py โ posts the edition to Discussions
generator/rotate.py โ advances the queues for the next edition
โ
public/ticker.svg
public/ticker-dark.svg
โ
โโโโโโโโโโโโโโโโบ openapi/<repo-python> / README
โโโโโโโโโโโโโโโโบ openapi/<repo-php> / README
โโโโโโโโโโโโโโโโบ openapi/<repo-js> / README
โโโโโโโโโโโโโโโโบ every other repository
.github/workflows/pulse.yml runs the whole cycle on a schedule and commits
the result back, every Monday at 13:00 Italian time. Each edition is named
after the ISO calendar week it goes out in.
Place this right after the title and the main badges:
<p align="center"> <a href="https://github.com/orgs/openapi/discussions"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/openapi/pulse/main/public/ticker-dark.svg"> <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/openapi/pulse/main/public/ticker.svg"> <img alt="Openapi Pulse" src="https://raw.githubusercontent.com/openapi/pulse/main/public/ticker.svg"> </picture> </a> </p>
The <picture> element gives the card a light and a dark variant so it sits
naturally in both GitHub themes. The whole image is one link, with one
destination โ the card carries several stories but never competes with itself.
Ordered queues decide what goes out. The first four are what the card shows; the last two are the blog relay described below. The entry at the top of each one is what goes out next, which makes curating them a single gesture: move a line to the top and it is on the next card. Publishing moves it to the bottom, so the queues keep turning on their own once you stop curating them.
| Queue | File | Source |
|---|---|---|
developers |
content/current.yml |
organization members |
contributors |
content/current.yml |
contributors registry |
apis |
content/apis.yml |
API library |
topics |
content/topics.yml |
open discussions |
news ยท insights |
content/blog.yml |
the Openapi blog |
sync.py aligns all of them with those sources:
python3 generator/sync.py # align the queues python3 generator/sync.py --dry-run # preview the changes
Membership belongs upstream; the running order belongs here. So the sync merges rather than overwrites โ entries already in a queue keep their position, newcomers are appended to the bottom so they queue behind everything already waiting instead of jumping the line, and anything no longer listed upstream is dropped. It never decides what goes out next.
The API library has no public JSON feed, so sync.py reads the server-rendered
listing and keys on the apiBox markup. If that page is ever restructured the
sync fails loudly rather than writing an empty queue.
The topic queue picks up every open discussion except the Openapi Pulse
editions themselves and the Announcements. Each entry carries a short โ the
label the card shows, since a track has room for roughly 35 characters and a
real discussion title rarely fits. Without one it falls back to the title, and
the fitter shrinks and clips it.
Anyone under exclude is filtered out of the people queues no matter what the
sources say. The card exists to give visibility to the people who work on and
with Openapi, not to the person publishing it, so the author of the system
stays out of his own rotation:
exclude: - francescobianco
python3 generator/sync.py # refresh the queues from their sources python3 generator/build.py # render the card for the top of each queue python3 generator/publish.py # post the edition, and relay the blog python3 generator/rotate.py # advance the queues for the next one
The order is not arbitrary. The card is built and committed before the post goes out, so the discussion can link the SVG at an immutable commit and keep showing the card it was published with instead of silently updating to a later edition. The queues are rotated after, which is what keeps the top of each file meaning "next". And because rotation comes last, a failed publish leaves the edition intact to be retried rather than silently skipped.
For the same reason rotate.py does not regenerate the SVGs: the card in
public/ has to keep showing the published edition until the next one is
built.
publish.py renders templates/discussion.md and opens one post per edition
in the Openapi Pulse category of
openapi/discussions. It then relays
the blog into two further categories โ see
the blog relay.
Two things GitHub does not let a script do, both worked around:
createDiscussionCategory mutation and no REST endpoint. The category has to
be created once by hand at
discussions/categories.
publish.py looks it up by name and stops with instructions if it is
missing, rather than quietly posting somewhere else.Repository.pinnedDiscussions is readable, but no mutation writes it. So
instead of pinning every new edition, one permanent discussion is pinned by
hand โ once, forever โ and its number recorded as discussions.index in
current.yml. publish.py rewrites that post's body every edition, so the
pinned entry always points at the latest one.The workflow needs a PULSE_DISCUSSIONS_TOKEN secret. The discussions live in
openapi/discussions, a different repository from this one, and a workflow's
built-in GITHUB_TOKEN is scoped to its own repository โ so a PAT with write
access to the discussions repository is required.
The Openapi blog is where the ecosystem already publishes editorial content, and Discussions is where the community reads it. Every edition carries one article from each of two blog categories into a category of its own:
| On the blog | In openapi/discussions |
|---|---|
| News | Announcements |
| API Insights | API Engineering |
What goes out is an extract, never a copy: the blog's own summary and a link back to the full piece. The article stays where it was written; Discussions gets the pointer and the conversation. No cover image โ a thread that opens on a full-width marketing image reads as a repost rather than as an invitation to talk.
The blog has no feed โ no RSS, no JSON, the pages are server-rendered โ so
generator/blog.py reads the listing markup, keying on the category badge and
the card heading. As with the API library, a restructured page yields nothing
and the sync stops loudly rather than emptying a queue.
These two queues behave differently from the other four, and the difference is the point:
publish.py moves what
it posted into relayed: at the bottom of content/blog.yml, and sync.py
never puts a relayed slug back.publish.py, not rotate.py. Rotation is for
queues that turn; this is a removal, and it belongs to whatever actually
managed to post. A relay that fails leaves its article at the top of the
queue for the next edition instead of burning it.The relay is deliberately the softer half of the edition. If a category does not exist yet, or the blog cannot be reached, the run says so and the edition itself still goes out โ the two are separate events that happen to share a schedule. Like every other discussion category, Announcements and API Engineering have to be created by hand once, at discussions/categories.
Both of them are also excluded from the card's topic queue: they hold what this system writes, and the card spotlights conversations, not broadcasts.
build | passing, the Pulse Card says this week in the community.build.py downloads https://github.com/<nickname>.png and
embeds it as a base64 data URI, clipped to a circle. Downloads are cached in
generator/.cache/; a nickname that cannot be fetched degrades to an
initial-letter monogram instead of breaking the build.prefers-reduced-motion. They carry the Openapi purple โ
#563e7d on light, lightened to #9c7ecc on dark, where the brand value
itself would all but disappear against #0d1117.@FrancescoRicchiutiOpenapi is 25
characters โ so a fixed budget would either truncate half the organization or
force every column to be sized for the worst case.OPENAPI PULSE type.raw.githubusercontent.com works today; GitHub Pages
(openapi.github.io/pulse/ticker.svg) or a dedicated endpoint would give
proper control over cache headers.openapi/contributors grows.See CARD.md for the full rationale behind the component.
One of the core Pulse mechanisms is the Repository of the Week.
Every week, Pulse can select a repository from the Openapi ecosystem and make it the focus of coordinated activity.
A weekly cycle may include:
Monday Select repository
Tuesday Maintenance / documentation
Wednesday Example or developer resource
Thursday Community / distribution
Friday Release and promotion
The exact process can evolve over time.
The important part is maintaining a predictable rhythm.
Pulse is intended to contain the configuration, workflows and data required to coordinate recurring ecosystem activity.
A possible structure is:
pulse/
โ
โโโ calendar/
โ โโโ weekly.yml
โ โโโ campaigns.yml
โ
โโโ repositories/
โ โโโ rotation.yml
โ โโโ priorities.yml
โ
โโโ campaigns/
โ โโโ ...
โ
โโโ templates/
โ โโโ release.md
โ โโโ repository-of-the-week.md
โ โโโ announcement.md
โ
โโโ metrics/
โ โโโ ...
โ
โโโ scripts/
โ โโโ ...
โ
โโโ .github/
โโโ workflows/
โโโ weekly-pulse.yml
โโโ release.yml
โโโ metrics.yml
โโโ ...
The structure is expected to evolve as Pulse grows.
Pulse provides a central place for automation that affects multiple Openapi repositories.
Whenever possible, common operations should be implemented as reusable workflows or shared automation rather than duplicated across repositories.
Individual repositories should remain focused on their products.
Pulse should focus on when, why and how the ecosystem acts as a whole.
Pulse activities can operate at different frequencies.
The main operational heartbeat.
Examples:
A broader ecosystem review.
Examples:
Temporary coordinated initiatives.
Examples:
Campaigns can temporarily modify the normal Pulse priorities without replacing the underlying weekly rhythm.
Pulse follows a few simple principles.
Consistency over intensity
Small activity every week is more valuable than occasional bursts of activity.
Automation over repetition
If an activity becomes predictable, Pulse should eventually automate it.
One ecosystem, many repositories
Repositories are independent projects, but they should behave as parts of the same Openapi developer ecosystem.
Useful activity over artificial activity
Pulse should never generate commits, releases or announcements merely to create noise.
Every Pulse should produce something useful for developers, contributors or users.
Measure and adapt
Activities should be measurable whenever possible.
What generates adoption should receive more attention. What does not work should be changed or removed.
Pulse is not a marketing campaign.
It is permanent infrastructure for maintaining the health, visibility and growth of the Openapi open-source ecosystem.
Over time, more recurring activities should become coordinated or automated through Pulse.
The desired result is simple:
Every week, something useful happens in the Openapi ecosystem.
That is the heartbeat.
That is Pulse.
openapi/pulse is a public repo on GitHub by openapi. ๐ The heartbeat and automation hub powering the @openapiยฎ open-source ecosystem.
It declares the MIT license on GitHub.
Its maker has not tagged a system, so it is unknown here. Its README says what it needs.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-11-16. GitHub counts 0 open issues and pull requests. Take My Repo does not judge from that whether it is maintained.
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.

Self-hosted AI coding assistant
Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype to production without rebuilding the stack.
๐ฆ A fully-featured and blazing-fast Rust API client to interact with @Openapiยฎ
๐ง A native GNOME knowledge workstation that turns documents into evolving AI-assisted knowledge bases.
๐ง A powerful, fully featured MCP Server for interacting with AI agents powered by @Openapiยฎ
๐ โจ Welcome to the Ultimate GitHub Christmas Party! โจ๐
๐ข A fully-featured and blazing-fast Node.js API client to interact with @Openapiยฎ
๐ A powerful, fully featured command-line interface and token manager for @Openapiยฎ
This page is also available as structured data, with the same sources and dates.
/api/v1/resources/gh/openapi/pulseTake My Repo has not tested this on your machine. Requirements come from the project's own documentation.