ci(meetings): keep the meeting archive current from the playlist - #55
Draft
Timur Tukaev (tym83) wants to merge 1 commit into
Draft
ci(meetings): keep the meeting archive current from the playlist#55Timur Tukaev (tym83) wants to merge 1 commit into
Timur Tukaev (tym83) wants to merge 1 commit into
Conversation
The archive only stayed accurate while someone remembered to append a row after each meeting, and it had already fallen a meeting behind. A weekly job now reads the playlist feed and opens a pull request with any recording that is not listed yet, leaving the Topics column for a human to fill in. Signed-off-by: tym83 <6355522@gmail.com>
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
1 participant
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.
Summary
The archive only stayed accurate while someone remembered to append a row after each meeting, and it had already fallen a meeting behind.
What
A weekly workflow reads the Atom feed of the community meetings playlist and opens a pull request with any recording that is not listed yet. Dates come from the publication date of the recording, snapped to the meeting's Thursday, because the day and month have been swapped often enough in video titles to make the title unreliable. The Topics column is left empty for a human to fill in from the notes.
Only meetings newer than the newest row are considered, so history is never rewritten. A cancelled meeting, or one held without a recording, produces nothing to detect — the archive now says so, and those rows stay a manual step for whoever ran or cancelled the meeting.
Why
No API key and no secret to provision: the playlist feed is public and carries the fifteen most recent entries, which is ample for a fortnightly meeting checked weekly. Nothing reaches
mainwithout review, and the job cannot invent a topic list.Preview
Verified against the current archive: a clean run reports no new recordings, and with the newest row removed the script restores it with the correct date derived from the publication date, and recomputes the counts line.