Conversation
There was a problem hiding this comment.
Pull request overview
Adds/updates meeting data used by the site’s calendar/next-meeting UI and the archive listing.
Changes:
- Updated the March 4, 2026 meeting subtitle (speaker name change) and added a new March 12, 2026 upcoming meeting entry.
- Added a new Spring 25-26 meeting entry to the archive, including a slides link.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/data/meetings.ts | Updates upcoming meeting metadata (subtitle) and adds a new upcoming meeting. |
| src/data/archive.ts | Adds a new archived meeting item (date, description, tags, slides link). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| title: "ACM x WIC: Leetcode and Art Night", | ||
| subtitle: "ACM joins Women in Computing for a Leetcode and art combo meeting!", |
There was a problem hiding this comment.
"Leetcode" is typically styled as "LeetCode" (brand capitalization). Consider updating the title/subtitle to match the official spelling for consistency.
| title: "ACM x WIC: Leetcode and Art Night", | |
| subtitle: "ACM joins Women in Computing for a Leetcode and art combo meeting!", | |
| title: "ACM x WIC: LeetCode and Art Night", | |
| subtitle: "ACM joins Women in Computing for a LeetCode and art combo meeting!", |
| ] | ||
| }, | ||
| { | ||
| date: new Date("03/04/2026"), |
There was a problem hiding this comment.
This entry uses a non-ISO date string ("03/04/2026"), but the file header comment says parsed date strings are ISO (YYYY-MM-DD). To avoid ambiguity in JS date parsing and keep docs accurate, consider switching this (and ideally the file) to ISO format or updating the header comment to match the actual accepted formats.
| date: new Date("03/04/2026"), | |
| date: new Date("2026-03-04"), |
No description provided.