Skip to content

feat(terraform-stack): colorize the plan summary by add/change/destroy - #347

Merged
prasad-manu merged 1 commit into
mainfrom
feat/colored-plan-summary
Sep 18, 2026
Merged

prasad-manu merged 1 commit into
mainfrom
feat/colored-plan-summary

Conversation

@prasad-manu

Copy link
Copy Markdown
Contributor

The plan comment's summary line was plain text ("Plan: N to add, N to change, N to destroy."), making it hard to scan at a glance across a PR that touches several stacks. Mirror the add/change/destroy counts with color-coded emoji (matching the convention terraform-core's own pipeline used before migrating here), while keeping the same underlying counts.

"No changes" is blue rather than green: this repo's own track-pending-release.yml already uses green to mean "zero outstanding", which would clash with green also meaning "N resources added" here.

The plan comment's summary line was plain text ("Plan: N to add, N to
change, N to destroy."), making it hard to scan at a glance across a PR
that touches several stacks. Mirror the add/change/destroy counts with
color-coded emoji (matching the convention terraform-core's own pipeline
used before migrating here), while keeping the same underlying counts.

"No changes" is blue rather than green: this repo's own
track-pending-release.yml already uses green to mean "zero outstanding",
which would clash with green also meaning "N resources added" here.

Requested by terraform-core during their migration to this workflow.
@prasad-manu
prasad-manu requested a review from a team as a code owner September 18, 2026 09:53
@prasad-manu
prasad-manu requested review from maoanran and removed request for a team September 18, 2026 09:53
@prasad-manu
prasad-manu merged commit 1db6f86 into main Sep 18, 2026
2 checks passed
@prasad-manu
prasad-manu deleted the feat/colored-plan-summary branch September 18, 2026 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants