[PR #843] [MERGED] ci: optimize workflows with parallel jobs and conditional checks #800

New issue

Closed

opened 2026-02-26 21:33:00 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 21:33:00 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/dreamhunter2333/cloudflare_temp_email/pull/843
Author: @dreamhunter2333
Created: 2/25/2026
Status: ✅ Merged
Merged: 2/25/2026
Merged by: @dreamhunter2333

Base: main ← Head: feature/email

📝 Commits (2)

3f9e33c ci: optimize workflows with parallel jobs and conditional checks
9327248 ci: add sync and tag triggers to frontend_pagefunction_deploy

📊 Changes

3 files changed (+140 additions, -32 deletions)

View changed files

📝 .github/workflows/frontend_deploy.yaml (+41 -20)
📝 .github/workflows/frontend_pagefunction_deploy.yaml (+25 -4)
📝 .github/workflows/tag_build.yml (+74 -8)

📄 Description

Summary

frontend_deploy.yaml: Split single job into deploy-frontend and deploy-telegram-frontend parallel jobs, each with secret-based conditional check
frontend_pagefunction_deploy.yaml: Added check job to skip deploy when PAGE_TOML secret is not configured
tag_build.yml: Split serial build into 3 parallel jobs (build-frontend, build-telegram-frontend, build-backend) + release job using artifacts

Test plan

Trigger tag_build.yml via tag push, verify all 3 build jobs run in parallel and release uploads correctly
Trigger frontend_deploy.yaml via tag push, verify both deploy jobs run in parallel
Trigger frontend_pagefunction_deploy.yaml manually, verify deploy is skipped when PAGE_TOML is not set

🤖 Generated with Claude Code

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/dreamhunter2333/cloudflare_temp_email/pull/843 **Author:** [@dreamhunter2333](https://github.com/dreamhunter2333) **Created:** 2/25/2026 **Status:** ✅ Merged **Merged:** 2/25/2026 **Merged by:** [@dreamhunter2333](https://github.com/dreamhunter2333) **Base:** `main` ← **Head:** `feature/email` --- ### 📝 Commits (2) - [`3f9e33c`](https://github.com/dreamhunter2333/cloudflare_temp_email/commit/3f9e33c7fb8fff160e4b2bcc68dd99c46ab92ce4) ci: optimize workflows with parallel jobs and conditional checks - [`9327248`](https://github.com/dreamhunter2333/cloudflare_temp_email/commit/93272483edf0843a7f4c6cd50febd84aaff26f4e) ci: add sync and tag triggers to frontend_pagefunction_deploy ### 📊 Changes **3 files changed** (+140 additions, -32 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/frontend_deploy.yaml` (+41 -20) 📝 `.github/workflows/frontend_pagefunction_deploy.yaml` (+25 -4) 📝 `.github/workflows/tag_build.yml` (+74 -8) </details> ### 📄 Description ## Summary - **frontend_deploy.yaml**: Split single job into `deploy-frontend` and `deploy-telegram-frontend` parallel jobs, each with secret-based conditional check - **frontend_pagefunction_deploy.yaml**: Added `check` job to skip deploy when `PAGE_TOML` secret is not configured - **tag_build.yml**: Split serial build into 3 parallel jobs (`build-frontend`, `build-telegram-frontend`, `build-backend`) + `release` job using artifacts ## Test plan - [ ] Trigger `tag_build.yml` via tag push, verify all 3 build jobs run in parallel and release uploads correctly - [ ] Trigger `frontend_deploy.yaml` via tag push, verify both deploy jobs run in parallel - [ ] Trigger `frontend_pagefunction_deploy.yaml` manually, verify deploy is skipped when `PAGE_TOML` is not set 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>