[GH-ISSUE #653] Create a GitHub workflow for SocratiQ #4156

Closed
opened 2026-04-19 12:09:52 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @profvjreddi on GitHub (Jan 25, 2025).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/653

Originally assigned to: @kai4avaya on GitHub.

We should develop a GitHub workflow that gets triggered on the main branch whenever we do a major update, or perhaps this should also happen on the dev branch for any sort of indexing of the content and so forth.

Originally created by @profvjreddi on GitHub (Jan 25, 2025). Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/653 Originally assigned to: @kai4avaya on GitHub. We should develop a GitHub workflow that gets triggered on the `main` branch whenever we do a major update, or perhaps this should also happen on the `dev` branch for any sort of indexing of the content and so forth.
GiteaMirror added the area: tools label 2026-04-19 12:09:52 -05:00
Author
Owner

@profvjreddi commented on GitHub (Apr 3, 2026):

Closing — SocratiQ's build and deployment process has evolved significantly since this was filed. If a specific CI/CD workflow is still needed, a fresh issue with current requirements would be more actionable.

<!-- gh-comment-id:4184848238 --> @profvjreddi commented on GitHub (Apr 3, 2026): Closing — SocratiQ's build and deployment process has evolved significantly since this was filed. If a specific CI/CD workflow is still needed, a fresh issue with current requirements would be more actionable.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/cs249r_book#4156