Use when a sponsor has rebranded or sent an updated logo and it must change on current and future events without altering how they appeared at past devopsdays events.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Sponsor logos and data are shared globally, so overwriting assets/sponsors/<c>/<id>.png would
retroactively change every event that sponsor has ever supported. This project deliberately does
not rewrite history — a 2018 event should still show the 2018 logo.
The fix is to keep the old logo under a date-stamped id, repoint past events at it, and give the new logo the original id so current and future events pick it up with no action from their organizers.
If this event is the only one that has ever listed the sponsor, just replace the image and open a normal PR. Check first:
grep -rl "id: <sponsor-id>" data/events/ | sort
One result → simple replacement. More than one → continue.
This is the one utility script worth calling directly: it takes arguments, has no interactive loop, and validates its inputs.
./utilities/change_sponsor_logo.sh <sponsor-id> /full/path/to/new-logo.png
Use the exact existing id as it appears in data/sponsors/, not the display name. The path to the
new image must be absolute.
It will:
assets/sponsors/<c>/<id>-before-<YYYYMMDD>.pngstatic/img/sponsors/<id>-before-<YYYYMMDD>.png (the legacy tree — this
filename pattern is the one exemption to the CI block on that directory)data/sponsors/<id>.yml to <id>-before-<YYYYMMDD>.ymlassets/sponsors/<c>/<id>.png with the new imageid: <sponsor-id> to id: <sponsor-id>-before-<YYYYMMDD>The script's idea of "past" is a path prefix match on the current calendar year, so it does not exclude future years. An event in a later year gets wrongly rewritten to the old logo.
git diff --stat
git diff -- data/events/ | grep '^[-+].*id:'
Then revert any event whose year is the current year or later:
git checkout -- data/events/2027/
Also check nothing was missed. The script enumerates through git ls-tree HEAD, so an event whose
data file is not yet committed is invisible to it:
git status --short data/events/
Update data/sponsors/<id>.yml with anything else that changed — a new name after a rebrand, a
new URL. The -before- copy keeps the old values for the old events.
Confirm the new logo meets the requirements: at least 200px wide (600px preferred), white or transparent background, and it really is a PNG.
data/sponsors/<id>-before-<date>.yml exists and has the old valuesstatic/img/sponsors/ changed except the -before-<date> file, or CI blocks
the PRFollow .claude/skills/submit-changes/SKILL.md.
PR title: [SITE] Update <Sponsor> logo, since this is not scoped to one event.
Mention in the PR body which events were repointed to the -before- id, so a reviewer can sanity
check the year boundary.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when adding, removing, or updating a local organizer on a devopsdays event team - covers the team_members entry, the photo, and the mandatory email to info@devopsdays.org that gates the merge.
The English summary is being prepared. Showing the original description.
Use when a devopsdays event has confirmed a speaker and their talk, workshop, ignite, or keynote needs to appear on the event site - covers the speaker bio page, the talk page, the headshot, and multi-speaker talks.
The English summary is being prepared. Showing the original description.
Use when a devopsdays event has sold or confirmed a sponsorship and the sponsor needs to appear on the event's site - covers both sponsors already in the shared directory and brand-new ones needing a logo and data file.
The English summary is being prepared. Showing the original description.
Use when a devopsdays event has finished and the slides or video recordings need to be attached to the talk pages, or when a speaker sends a link to their deck afterwards.
The English summary is being prepared. Showing the original description.
Use when building or editing a devopsdays event's schedule - adding talks, ignites, open spaces, breaks, and evening events to the program, or moving time slots around.
The English summary is being prepared. Showing the original description.
Use when a devopsdays event that is already listed on the site has to be cancelled or postponed, and its pages need to stop advertising dates, registration, and sponsorship.
The English summary is being prepared. Showing the original description.