Set the original colour scheme's typeface and palette to the 1987
Docklands Light Railway P86/P89 stock.
- Use the Rockwell slab serif (the original DLR branding typeface) for the
original theme, with Rokkitt loaded as a free fallback for systems
without Rockwell installed.
- Flip the palette to be blue-dominant: blue body/skirt as the field, red
band/doors as the accent, white stripes, matching the rolling stock.
Apply path filters to the push (merge-to-main) trigger only, so merges that
do not change the image (CI/Renovate config, docs) skip the build and release.
Pull requests keep running unfiltered so the required check is always reported.
Add a concurrency group keyed by ref with cancel-in-progress, so a newer run
supersedes an older in-flight run: a fresh merge to main cancels the previous
build and only the most recent release is produced, avoiding tags that would
be immediately replaced.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add a packageRule that automerges patch and minor updates, with
platformAutomerge enabled so Gitea merges them once required checks pass.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Join the two theme options into a single rounded container with the active
segment filled and a divider between them, replacing the two separate pills.
Markup and aria-pressed behaviour are unchanged.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-12 11:34:32 +01:00
4 changed files with 60 additions and 21 deletions
"description":"Commit every update as fix(deps) so each merged Renovate PR triggers a patch release. config:recommended pulls in :semanticPrefixFixDepsChoreOthers, which forces non-npm updates (Docker, Actions) to chore and would otherwise produce no release.",
"matchPackageNames":["*"],
"semanticCommitType":"fix"
},
{
"description":"Auto-merge patch and minor updates once checks pass.",
/* Segmented control: both options joined in one rounded container,
with the active segment filled. */
.theme-toggle{
display:flex;
gap:0.5rem;
border:none;
display:inline-flex;
border:2pxsolidvar(--button-bg);
border-radius:999px;
overflow:hidden;
margin:0;
padding:0;
}
@@ -75,19 +82,22 @@ body {
font-family:inherit;
font-size:0.9rem;
font-weight:600;
padding:0.5rem1rem;
border:2pxsolidvar(--button-bg);
border-radius:999px;
padding:0.5rem1.1rem;
border:none;
background:transparent;
color:var(--text);
cursor:pointer;
transition:background0.2sease,color0.2sease;
}
/* Divider between the two segments. */
.theme-button+.theme-button{
border-left:2pxsolidvar(--button-bg);
}
.theme-button[aria-pressed="true"]{
background:var(--button-active-bg);
color:var(--button-active-text);
border-color:var(--button-active-bg);
}
.stage{
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.