fix: preserve past Discord events across automation runs#139
Merged
kordianbruck merged 1 commit intomasterfrom Apr 11, 2026
Merged
fix: preserve past Discord events across automation runs#139kordianbruck merged 1 commit intomasterfrom
kordianbruck merged 1 commit intomasterfrom
Conversation
Agent-Logs-Url: https://github.com/TUM-Dev/Website/sessions/3a7331eb-55ee-415a-8a9d-75159579f4b8 Co-authored-by: kordianbruck <298860+kordianbruck@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
kordianbruck
April 11, 2026 12:27
View session
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
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.
The
fetch-event-node.ymlworkflow checked out the default branch (which has noscheduled_events.json) before running the script. Since the Discord API only returns active/upcoming events, the merge inget_events.jsalways started from an empty baseline — discarding all previously accumulated past events on every run.Changes
.github/workflows/fetch-event-node.yml: Added a step before the script runs that fetchesscheduled_events.jsonfrom theevent-databranch into the workspace, so the existing merge logic can accumulate events correctly over time:The
|| trueguards handle the first-run case where theevent-databranch or file doesn't yet exist. No changes toget_events.jswere needed — its merge logic was already correct.