tr
TryGhost
GitHub
Ghost
Workspace
GitHub
CI Pipeline Executions
Filtered
Runs
Demo
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Overview
⌘K
Ghost
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
GitHub
Ghost
Workspace
Succeeded
30356
cde47614 Added a Bluesky share button to the Ember post success modal ref https://linear.app/ghost/issue/DES-1367/add-bluesky-share-button-to-published-post-popup The React posts list already has this modal, but it is still behind a flag, so the Ember one is what publishers see after publishing today. Leaving it out would mean Bluesky comes and goes depending on which list the post was published from. The intent URL and its payload match the React modal and Portal's native share, so a post shared from any of them composes the same post. Bluesky goes last to keep the order of the four existing buttons. In dark mode it keeps its brand colour like Facebook and LinkedIn rather than joining the rule that recolours the monochrome X and Threads marks. A fifth button did not fit the existing layout. The row was a fixed four-column grid, so it now takes its track count from the number of buttons. The chips also ask for 56px but were held at 64px by the generic footer button min-width, which made the five of them wider than the 478px the modal has to spend and wrapped the copy link label onto a second line; clearing that min-width lets the declared width apply. Below 500px the grid dropped to two columns, which leaves a hole in the last row with an odd number of buttons. They now stay on one row and fill the width, the same as the React modal at that size.
by Sodbileg G...
S
Succeeded
30356
927d6766 Added a Bluesky share button to the Ember post success modal ref https://linear.app/ghost/issue/DES-1367/add-bluesky-share-button-to-published-post-popup The React posts list already has this modal, but it is still behind a flag, so the Ember one is what publishers see after publishing today. Leaving it out would mean Bluesky comes and goes depending on which list the post was published from. The intent URL and its payload match the React modal and Portal's native share, so a post shared from any of them composes the same post. Bluesky goes last to keep the order of the four existing buttons. In dark mode it keeps its brand colour like Facebook and LinkedIn rather than joining the rule that recolours the monochrome X and Threads marks. A fifth button did not fit the existing layout. The row was a fixed four-column grid, so it now takes its track count from the number of buttons. The chips also ask for 56px but were held at 64px by the generic footer button min-width, which made the five of them wider than the 478px the modal has to spend and wrapped the copy link label onto a second line; clearing that min-width lets the declared width apply. Below 500px the grid dropped to two columns, which leaves a hole in the last row with an odd number of buttons. They now stay on one row and fill the width, the same as the React modal at that size.
by Sodbileg G...
S
Succeeded
bluesky-share-DES-1367
dbbe1b12 Merge 7a3c9aa1170a0e8c3001b8e7b758b59220572c77 into b9b4a95d39bdae49e4bc02cf4ddcdb457f22dbd8
by Sodbileg G...
S
Failed
30356
7a3c9aa1 Changed share buttons to fill the row when the modal footer stacks ref https://linear.app/ghost/issue/DES-1367/add-bluesky-share-button-to-published-post-popup Below sm the dialog footer stacks, so the copy button spans the full width but the social buttons kept their fixed width and left a gap on the right that read as a missing button. They now grow to fill the row at that width and return to the fixed width at sm, on the same breakpoint the footer itself switches on.
by Sodbileg G...
S
Previous
Next