Shortcut to publish library and automatically update files

Wow, still not implemented. Is anyone from the Figma team there? Please pause the FigJam features and put the power into this obvious feature. Not all users work entirely in enterprise teams.

Hey All, thanks for the feedback!

This is on our radar, but we donā€™t have an exact timeline we can provide at this time. Weā€™ll continue to pass your feedback and Votes onto the team for future consideration.

6 Likes

This would be super userful for power users. Espacially in intial phases of setting up a library.
Even putting it in the menu would help on macOS as every menu item can be assigned to a keyboard shortcut.

Thanks :pray:t2:

Iā€™m looking for a quick way to update all components in my file.

Iā€™m building out a library of components, which is a fairly iterative process. Every time I update a component in the library, in my main design file I have to click assets > library > updates > update all to import the new components. Itā€™s ā€œonlyā€ four clicks but Iā€™m doing it often enough that itā€™s driving me kinda nuts.

Iā€™d love to see a quick access option for this action, either a keyboard shortcut or a button that just pulls in all the updates in one click.

1 Like

It would be really useful to have a publish button near the share button. Publishing a library is one of the main actions of that type of file, but right now itā€™s not very accessible.

This is really bothering me as well. I am a single designer in a growing startup working with one design system file linked to many other files. DId anyone find a solution that works for them?

As someone who is constantly building and maintaining libraries, the workflow to publish every time I make a few changes is too long, cumbersome, and inaccessible with a keyboard macro! Itā€™s nice that you prompt me to review all my changes before pushing it, but that shouldnā€™t slow my process down.

Similarly, when in a design file, let me pull all the library updates with one click or keyboard shortcut!

TLDR make shortcuts or definite keystrokes for publishing and accepting library updates!

3 Likes

Hey guys, am I missing something? How is this not a huge painpoint for everyone? Is it different on the organizational plan? We have the professional plan. Figma pushed out so many new features just now which are awesome, but they havenā€™t fixed this basic thing that is a huge painpoint in my everyday workflow.

Figma please :pleading_face::point_right::point_left:

What is the difference on enterprise teams? If I upgrade Figma would this problem be resolved?

Please add a shortcut to publish selected component

Hello, the [Enter] shortcut was added in the UI redesign in order to confirm ā€˜inserting a componentā€™.

image

Can we please pleaaase, add the same to the ā€˜Publishā€¦ā€™ and ā€˜Update allā€™ buttons as well?

This would save so much cumulated time!

+1. This is a no brainer

+1, absolutely needs to be solved

2 Likes

+1, please this is really needed. It would save everyone much time and energy.

+1. Absolute necessity

+1 - absolute banger

Canā€™t wait to have this!

Pleeeeease add this! I spend so much of my day publishing and updating.

I really wish we could opt-in to auto-updates from specific libraries for specific files.

We have lots of design files that are on ā€œmaintenance modeā€. They are required for occasional reference and should reflect our latest design system version, but they are not in active build or testing.

It would save so much time for designers during quarterly maintenance cycles for our artifacts. Itā€™d be better for us to receive a cue that auto-updates have been applied, instead of waiting for a designer to enter the file in order to apply them. In the rare instance an auto-update caused a breaking change we could roll it back in version history.

The risk of a breaking change is low because we have a great design systems team. We spend the time on a great design system and standards for implementation to minimize risk during updates, so we shouldnā€™t have to spend more time making manual updates to each file (especially low-priority ones) when an update is published.