ci(deploy): post PR status comments and store deployment info#442
Merged
Conversation
At the start of every push-triggered Deploy run: - Find the merged PR associated with the head commit via GitHub API - Post '🚀 Starting production deploy...' on that PR After a successful build: - Write build_production/_deployment-info.json with commit_sha, pr_number, pr_title, repository and timestamp so the WordPress sync handler can post a 'finished' comment after the fragments are updated. Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
Contributor
|
🚀 Starting production deploy of site header and footer fragments... |
Contributor
|
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
1 participant
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.
What
🚀 Starting production deploy...comment on the PR that triggered the deploy (push events only)build_production/_deployment-info.jsonwithcommit_sha,pr_number,pr_title,repositoryandtimestampafter the buildWhy
Provides deploy status visibility directly in the PR timeline. The
_deployment-info.jsonfile is served athttps://libresign.coop/_deployment-info.jsonafter the GitHub Pages deployment and is consumed by the WordPress webhook handler (see companion PR inwordpress-theme) to post a✅ fragments syncedcomment after the sync completes.How it works