Remove unused listserv pipeline workflow#9
Open
DIodide wants to merge 1 commit into
Open
Conversation
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.
Summary
Removes the unfinished listserv email ingestion pipeline runtime from the app:
Pipeline PollGitHub Actions workflow/pipelinerouter and implementation moduleslistserv_configs/pipeline_logsschema exports while keeping thelistserv_emailsarchive table used by scraper/import toolingMotivation
The
Pipeline Pollworkflow was intended to periodically hit/pipeline/pollfor an email/listserv ingestion system. That system was never fully implemented or configured, so the workflow was effectively dead code. On the oldDIodide/TheForumfork, it was running on a schedule with missing secrets and repeatedly failing by calling an emptyFASTAPI_URL(/pipeline/poll), creating noisy GitHub failure notifications.Since future work should happen in
TigerAppsOrg/TheForum, this PR removes the workflow and the dead runtime surface from the organization repo so the unfinished pipeline cannot be accidentally reactivated there. The standalone listserv scraper/archive work is left intact because it is separate from the broken scheduled FastAPI pipeline.Operational note: I also manually disabled the active
Pipeline Pollworkflow onDIodide/TheForumto stop the existing notification loop.Verification
uv run python -c "from app.main import app; print([route.path for route in app.routes])"uv run ruff check appbun --filter @the-forum/database check-typesbun --filter @the-forum/web check-types