refactor(monorepo): move workflow to correct location #253
+59
−75
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
Contributor
Author
How to use the Graphite Merge QueueAdd the label graphite/merge to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
ezavada
approved these changes
Oct 16, 2025
Contributor
Merge activity
|
# Enhance Auto-Deploy Workflow with Better Logging and Status Tracking ## Overview This PR enhances the auto-deploy GitHub workflow by improving status tracking and adding detailed logging for deployment processes. It provides better visibility into deployment progress and failures. ## Brief Changelog - Added explicit GitHub token to workflow actions - Improved JSON handling for input parameters using `toJson` - Enhanced status tracking with per-project state monitoring - Added detailed logging for deployment progress and completion status - Implemented tracking of last reported terminal state per project to avoid duplicate logs - Added visual indicators (✅/❌) for successful and failed deployments - Removed duplicate workflow file from incorrect location ## Testing and Verifying This change can be verified by running the auto-deploy workflow and observing the improved logs in the GitHub Actions console, which now show clear progress indicators, success/failure counts, and detailed per-project status updates.
graphite-app
bot
force-pushed
the
Anthony/move-workflow
branch
from
1604228 to
e0e4ede
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #253 +/- ##
==========================================
- Coverage 40.49% 39.93% -0.56%
==========================================
Files 100 100
Lines 7046 7046
==========================================
- Hits 2853 2814 -39
- Misses 3890 3938 +48
+ Partials 303 294 -9 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Enhance Auto-Deploy Workflow with Better Logging and Status Tracking
Overview
This PR enhances the auto-deploy GitHub workflow by improving status tracking and adding detailed logging for deployment processes. It provides better visibility into deployment progress and failures.
Brief Changelog
toJsonTesting and Verifying
This change can be verified by running the auto-deploy workflow and observing the improved logs in the GitHub Actions console, which now show clear progress indicators, success/failure counts, and detailed per-project status updates.