feat: automate meeting notes → GitHub Discussion + Slack notification#7
Open
charlieforward9 wants to merge 2 commits intoopenjs-foundation:mainfrom
Open
Conversation
added 2 commits
March 4, 2026 17:13
- Add `.github/workflows/post-meeting-notes.yml`: triggers on merge of any `meetings/YYYY-MM-DD.md` file, collects releases from all OpenVis project repos (deck.gl, kepler.gl, cosmos.gl, perspective, geoda.ai) over the past 15 days, posts a GitHub Discussion, and notifies Slack - Add `meetings/TEMPLATE.md` for consistent meeting notes format - Add `ROADMAP.md` with admin prereqs checklist, ongoing workflow, repo list, and stretch goal (website auto-update PR) - Update `media.md` with structured YouTube and summit links - Update `README.md` to link Roadmap and Discussions
After the Discussion is posted, a second job opens a PR on openjs-foundation/open-visualization prepending an entry to content/news.json so the meeting appears on openvisualization.org. Requires a WEBSITE_PAT secret with repo scope on open-visualization. Updates ROADMAP.md with the website JSON schema and setup step.
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
Adds a GitHub Actions workflow that turns each bi-weekly meeting notes commit into a GitHub Discussion (with an auto-generated release summary) and a Slack notification — zero manual steps after the PR merge.
What's included
.github/workflows/post-meeting-notes.yml— the automation:meetings/YYYY-MM-DD.mdfile is merged intomain#open-visualizationon Slack with the Discussion URLmeetings/TEMPLATE.md— consistent template for meeting contributors (slides link, recording link, agenda, notes)ROADMAP.md— full checklist of admin prereqs, ongoing workflow, repo list, and the stretch goal belowmedia.md— cleaned up with structured YouTube and summit linksREADME.md— links to Roadmap and Discussions addedAdmin prerequisites (one-time, before merging the first meeting notes file)
SLACK_WEBHOOKsecret — repo Settings → Secrets and variables → ActionsStretch goal (tracked in ROADMAP.md)
After each meeting, also open a PR on openjs-foundation/open-visualization to add the meeting to the website blog/news section — making the latest org status as indexable as possible.
🤖 Generated with Claude Code