Draft: feat: Added Github CI to trigger pubgrade

[akash2237778]

Description

Fixes #(issue)

Checklist

• My code follows the contributing guidelines of this project.
• I am aware that all my commits will be squashed into a single commit, using the PR title as the commit message.
• I have performed a self-review of my own code.
• I have commented my code in hard-to-understand areas.
• I have updated the user-facing documentation to describe any new or changed behavior.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• I have not reduced the existing code coverage.

Comments

Summary by Sourcery

New Features:

• Add a GitHub Actions workflow to trigger Pubgrade builds on pushes to main and add-ci branches

[changeset-bot]

⚠️ No Changeset found

Latest commit: 724abf2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sourcery-ai]

Reviewer's Guide

This PR adds a new GitHub Actions workflow (.github/workflows/pubgrade.yml) that triggers a pubgrade build via an API call whenever code is pushed to the main or add-ci branches.

Sequence diagram for GitHub Actions workflow triggering pubgrade build

sequenceDiagram
    participant Dev as Developer
    participant GitHub as GitHub
    participant Actions as GitHub Actions
    participant Pubgrade as pubgrade API
    participant DockerHub as DockerHub

    Dev->>GitHub: Push to main/add-ci branch
    GitHub->>Actions: Trigger workflow
    Actions->>Actions: Checkout repository
    Actions->>Actions: Get repo, branch, version
    Actions->>Pubgrade: Send build trigger (cURL, tokens)
    Pubgrade->>DockerHub: Build and push Docker image
    Pubgrade-->>Actions: Build status

Loading

Flow diagram for new pubgrade build trigger process

flowchart TD
    A[Push to main/add-ci branch]
    B[GitHub Actions workflow starts]
    C[Checkout repository]
    D[Get repo/branch/version]
    E[Trigger pubgrade build via API]
    F[pubgrade builds Docker image]
    G[Image pushed to DockerHub]

    A --> B --> C --> D --> E --> F --> G

Loading

File-Level Changes

Change	Details	Files
Introduce pubgrade trigger CI workflow	Configure workflow to run on push to main and add-ci branches Checkout repository using actions/checkout@v4 Extract repository name, branch name, and version via shell commands into environment variables Invoke pubgrade build endpoint with a cURL POST request, passing project token, Docker Hub token, and build payload	.github/workflows/pubgrade.yml

Possibly linked issues

• #0: The PR adds a GitHub CI workflow that triggers a build, directly contributing to the issue's goal of setting up CI/CD.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
elixir-cloud-components	Ready	Preview, Comment	Jan 6, 2026 1:14pm

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• The "Get repository name" step sets REPO_NAME but it’s never used in the workflow—consider removing it.
• Add set -e at the top or use curl -f in the trigger step to ensure the job fails on non-2xx HTTP responses.
• Guard against git describe failing when there are no tags or returning dirty suffixes by providing a fallback version or cleaning its output.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments
- The "Get repository name" step sets REPO_NAME but it’s never used in the workflow—consider removing it.
- Add `set -e` at the top or use `curl -f` in the trigger step to ensure the job fails on non-2xx HTTP responses.
- Guard against `git describe` failing when there are no tags or returning dirty suffixes by providing a fallback version or cleaning its output.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[anuragxxd]

Is it safe to merge @akash2237778 ?