Remove legacy Gemini podcast content-generation hook - #207
Merged
Conversation
Delete the content-generation Directus action hook that fired on podcasts.items.update and called Gemini to write draft shownotes and social posts into podcast_generated_content. Removes the hook and its generateContent module, drops the manifest entry from the bundle package.json, and removes the now-unused fetchSlackContext helper (only imported by the removed generator). Shared helpers gemini.ts and templateRenderer.ts are kept because the asset generator still uses them.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
Pull request overview
Removes the legacy Directus hook that automatically called Gemini to generate podcast shownotes/social drafts on transcript updates, aligning the CMS bundle with the new agent-driven generation flow (out of scope here).
Changes:
- Deleted the
content-generationhook entrypoint and its Gemini generation implementation. - Removed the Slack-context helper that was only used by the deleted generator.
- Unregistered the
content-generationentry from the Directus extension bundle manifest.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| directus-cms/extensions/directus-extension-programmierbar-bundle/src/shared/fetchSlackContext.ts | Removed Slack message aggregation helper that was only used by legacy content generation. |
| directus-cms/extensions/directus-extension-programmierbar-bundle/src/content-generation/index.ts | Removed the Directus action hook that triggered Gemini generation on transcript updates. |
| directus-cms/extensions/directus-extension-programmierbar-bundle/src/content-generation/generateContent.ts | Removed the Gemini-based shownotes/social generation implementation and its CMS writes. |
| directus-cms/extensions/directus-extension-programmierbar-bundle/package.json | Removed the content-generation hook from directus:extension.entries so it’s no longer loaded. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Requested by Dennis Becker · Slack thread
Before / After
Before: editing a podcast's transcript in Directus automatically triggered a Gemini call. The
content-generationaction hook fired onpodcasts.items.updatewhenevertranscript_textwas set, read theai_prompts, rendered the templates, and wrote draft shownotes and social posts intopodcast_generated_content(those drafts were never auto-approved).After: that automatic Gemini generation is removed. Nothing auto-generates when a transcript is edited anymore. Shownotes/social generation is being moved to an agent-driven flow, which is out of scope for this PR.
How
src/content-generation/index.tsandsrc/content-generation/generateContent.ts.content-generationentry from the bundle manifest (directus:extension.entriesinpackage.json).src/shared/fetchSlackContext.ts, which was imported only by the deleted generator (no other file references it).src/shared/gemini.tsandsrc/shared/templateRenderer.tsare deliberately kept — the cover/asset generator (asset-generation) still uses them, andGEMINI_API_KEYis still required for that.content-approvalhook is left in place but becomes dormant: nothing writespodcast_generated_contentanymore, so it has nothing to act on. It can be removed in a follow-up if desired.The extension bundle build was verified with
npm run build(directus-extension build) after the removal — it completes successfully and no reference to the removed module remains.Generated by Claude Code