Specify button order per priority per context for empty states
While button design specs read that primary buttons should be placed on right, which is ok for modals and top area navigation items, most empty states have historically placed the primary button on the left when there's more than one option (see gitlab-ce!22745, gitlab-ee!7358, gitlab-ee!7967, and more).
Buttons are ordered by importance from right to left. This means primary buttons are always on the right followed by secondary buttons etc. As an effect it means buttons with dismissive actions are on the left and buttons with affirmative actions are on the right. Depending on the context, the primary, affirmative action may be destructive.
The recently added gitlab-ce!24549 followed the guideline above but seems to be in contrast with the rest of the empty states across the platform. See discussion in gitlab-ce!24549 (comment 135113852). Button design specs also inlcude positioning guidelines like the following:
Buttons are positioned towards the right and are placed next to each other when there are multiple. This applies to buttons with affirmative, dismissive, and destructive actions.
Either a) include a guideline for ordering the primary button to the left when the butons are centered or left-aligned or b) move all primary buttons on empty states to the right.