Skip to content

feat(ci): add comment on pr workflow#663

Open
riteshfyi wants to merge 2 commits intowebex:nextfrom
riteshfyi:neon
Open

feat(ci): add comment on pr workflow#663
riteshfyi wants to merge 2 commits intowebex:nextfrom
riteshfyi:neon

Conversation

@riteshfyi
Copy link
Copy Markdown
Contributor

@riteshfyi riteshfyi commented Mar 27, 2026

COMPLETES #<SPARK-793038>

This pull request addresses

add a workflow to comment on merged pr's with the changes in versions & changelog url

by making the following changes

< DESCRIBE YOUR CHANGES >
wrote a workflow in deploy.cd

Change Type

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Tooling change
  • Internal code refactor

The following scenarios were tested

  • Tested Locally on my Fork branch, mocked the deploy.cd jobs to simulate the action.
Screenshot 2026-03-27 at 4 25 20 PM

The GAI Coding Policy And Copyright Annotation Best Practices

  • GAI was not used (or, no additional notation is required)
  • Code was generated entirely by GAI
  • GAI was used to create a draft that was subsequently customized or modified
  • Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
  • Tool used for AI assistance (GitHub Copilot / Other - specify)
    • Github Copilot
    • cursor - claude opus 4.6
  • This PR is related to
    • Feature
    • Defect fix
    • Tech Debt
    • Automation
    • CI

Checklist before merging

  • I have not skipped any automated checks
  • All existing and new tests passed
  • [] I have updated the testing document
  • I have tested the functionality with amplify link

Make sure to have followed the contributing guidelines before submitting.

@riteshfyi riteshfyi requested a review from a team as a code owner March 27, 2026 10:44
@riteshfyi
Copy link
Copy Markdown
Contributor Author

riteshfyi commented Mar 27, 2026

Test Comment Link : riteshfyi#5 (comment)

@aws-amplify-us-east-2
Copy link
Copy Markdown

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-663.d1b38q61t1z947.amplifyapp.com

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8155fa67cb

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

.filter(([pkg]) => packageVersions[pkg])
.map(([pkg, prefix]) => {
const tag = `${prefix}-v${packageVersions[pkg]}`;
return `[\`${tag}\`](${repoUrl}/releases/tag/${tag})`;
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Link pushed tags to tag pages instead of releases

The PR comment builds tag links as .../releases/tag/${tag}, but in the workflows I inspected this pipeline only creates and pushes Git tags (no GitHub Release creation step). In that setup, releases/tag/... URLs can point to missing release pages, so the “Released in” links in the comment break for contributors. Point to tag URLs (for example /tree/${tag} or /tags) or create releases before using release URLs.

Useful? React with 👍 / 👎.

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.

1 participant