A token pipeline or an icon library can generate every file and still depend on a manual hand-off: someone has to notice that Figma changed and start the export. An automatic pull request removes that step but keeps the review: the change still waits for a person to merge it.
How it works in FISYCO
Automatic pull requests apply to icons, illustrations and tokens libraries. The setting appears when the workspace plan includes it. With it on, a design change travels like this:
- Someone publishes the library in Figma. With Figma webhooks connected, that starts a sync. Without them, Check now on the library page starts it.
- After every successful sync, FISYCO creates the library's pull request or updates the open one.
- The team reviews and merges it as usual.
While a pull request is open, new changes go into it as another commit. The team reviews one pull request per library, not a pile of them. If that pull request was merged or closed in the meantime, FISYCO opens a new one. While the setting is on, FISYCO doesn't accept manual pull requests for that library.
An automatic pull request also goes out when the generated files change without a Figma change, for example after someone edits a naming template. Repository webhooks bring the status back to FISYCO: open, merged, closed, or replaced by a later sync.
What stays manual
The merge. FISYCO never writes to the target branch directly, and nothing in the product approves a change for the team. Fixes for differences reach code the same way, as a design system patch.
Related
- Review changes and pull requests: turning automatic pull requests on, branch names and labels.
- Design system patch
- Design tokens from Figma to code without manual exports