-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update planpreview comment format #4101
Conversation
@@ -178,11 +178,13 @@ func makeCommentBody(event *githubEvent, r *PlanPreviewResult) string { | |||
b.WriteString(fmt.Sprintf(hasChangeTitleFormat, event.HeadCommit, len(r.Applications))) | |||
|
|||
changedApps, pipelineApps, quickSyncApps := groupApplicationResults(r.Applications) | |||
if len(changedApps)+len(pipelineApps)+len(quickSyncApps) > 0 { | |||
b.WriteString("\n## Plans\n\n") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
b.WriteString("\n## Plans\n\n") | |
b.WriteString("\n## Plans Preview\n\n") |
how about this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
umm, if u wanna do this, I feel Plan Preview
or Plan Previews
are more natural.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then I think I will go with Plan Preview
but it's up to you 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO, I feel Plans
is enough because this action is planpreview, so let's keep this. 🙌
* Update planpreview comment format * fixup
* Fix to return an error when not finding the last commit (#4100) * Update planpreview comment format (#4101) * Update planpreview comment format * fixup * Update the planpreview format (#4103) * Remove deprecated envName field (#4105) * Release v0.41.2 (#4111) * Release v0.41.2 * Update the release note Co-authored-by: Khanh Tran <[email protected]>
What this PR does / why we need it:
Before
①
②
After
①
②
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: