chore(sync): record the tickserv showcase entry as a no-op - #494
Merged
Conversation
Ports nuxt/ui `b751eaef` (#6869) as a no-op: two lines in upstream's `showcase.yml` plus a screenshot, adding a site built with Nuxt UI to their gallery. This fork keeps its own `showcase.yml` listing sites built with Bitrix24 UI, so the entry is content rather than code. Checked for the one thing that would make it more than that — it uses no field we lack: `name` and `url` are the two required keys of our own schema in `docs/content.config.ts`, which already carries `screenshotUrl` and the full `screenshotOptions` object as well. Same call as `d0cfc2b1`, `78cc1ce5`, `cf5f15e3`, `2beb2345`, `a630c943` and `a7f26a32`. The one showcase commit that was **not** a no-op is `f6d188bd`, which introduced `screenshotOptions` — a schema change, and therefore shared. This one introduces nothing. Ledger: cursor → `b751eaef` (upstream HEAD), parity snapshot refreshed.
3 tasks
IgorShevchik
added a commit
that referenced
this pull request
Aug 25, 2026
The entry was written with `pending-merge` because the PR carrying it had not merged yet; it now points at #494 and its squash SHA `2e45e257`. No entry in the ledger is left unreconciled, and the cursor `b751eaef` is upstream HEAD. Bookkeeping only — no source, test or docs change. Co-authored-by: Shevchik Igor <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Linked issue
Sync with
nuxt/ui@v4—b751eaef(nuxt/ui#6869). After this the cursor is at upstream HEAD.Type of change
Description
Two lines in upstream's
docs/content/showcase.ymlplus a screenshot, adding a site built with Nuxt UI to their gallery:This fork keeps its own
showcase.ymllisting sites built with Bitrix24 UI, so the entry is content rather than code.Checked for the one thing that would make it more than content — it uses no field we lack.
nameandurlare the two required keys of our own schema indocs/content.config.ts, which already carriesscreenshotUrland the fullscreenshotOptionsobject (delay,width,cookies,removeElements) as well. Nothing structural to take.Same call as
d0cfc2b1,78cc1ce5,cf5f15e3,2beb2345,a630c943anda7f26a32. The one showcase commit that was not a no-op isf6d188bd, which introducedscreenshotOptions— a schema change, and therefore shared. This one introduces nothing.Recorded rather than skipped silently so the next porter does not re-derive it.
Verification
Ledger only — no source, test or docs change. Cursor →
b751eaef, which is upstream HEAD; parity snapshot refreshed to it with zero package differences, andtest/utils/dep-parity.spec.tspasses in full (22 assertions).Checklist
Generated by Claude Code