Update and rename docker-image.yml to docker.yml

[Dargon789]

Motivation

Solution

PR Checklist

• Added Tests
• Added Documentation
• Breaking changes

Summary by Sourcery

Streamline the Docker CI workflow by renaming the file and enhancing it with scheduled runs, Buildx multi-platform builds, metadata tagging, conditional pushes, and automated image signing with Cosign.

CI:

• Rename and replace the legacy docker-image.yml workflow with docker.yml
• Add scheduled cron runs and triggers on pushes to master, semver tags, and PRs
• Configure Docker Buildx for multi-platform builds with cache
• Extract Docker metadata and conditionally push images to GHCR on non-PR events
• Install Cosign and sign published Docker images using ephemeral identity tokens

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
next	Ready	Preview	Comment	Oct 26, 2025 3:21pm
react	Ready	Preview	Comment	Oct 26, 2025 3:21pm

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[sourcery-ai]

Reviewer's Guide

The PR renames the existing Docker workflow file and replaces it with a consolidated docker.yml that defines scheduled, push, and pull_request triggers, sets environment variables for registry and image name, and implements a build job using Buildx, cosign, and metadata actions to build, cache, push, and sign Docker images.

Flow diagram for Docker image build and sign process in workflow

flowchart TD
  Start(["Workflow Triggered (push, pull_request, schedule)"]) --> Checkout["Checkout Repository"]
  Checkout --> Buildx["Set up Docker Buildx"]
  Buildx --> Metadata["Extract Docker Metadata"]
  Metadata --> BuildPush["Build and Push Docker Image"]
  BuildPush -->|if not pull_request| Sign["Sign Docker Image (cosign)"]
  BuildPush --> Registry["Push to Docker Registry"]
  Sign --> Registry

Loading

File-Level Changes

Change	Details	Files
Rename and replace the Docker workflow file	Delete the old docker-image.yml Add a new workflow file named docker.yml	.github/workflows/docker-image.yml .github/workflows/docker.yml
Update triggers and environment variables	Add schedule cron trigger Enable push triggers on master and semver tags Enable pull_request trigger on master Define REGISTRY and IMAGE_NAME env vars	.github/workflows/docker.yml
Implement comprehensive build-and-sign job	Checkout the repository Install cosign tool when not in PR Set up Docker Buildx builder Log into the registry when not in PR Extract Docker metadata (tags, labels) Build and push Docker image with cache Sign the published Docker image	.github/workflows/docker.yml

---

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.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[sourcery-ai]

Hey there - I've reviewed your changes and found some issues that need to be addressed.

• The jobs.build section looks mis-indented—runs-on, permissions, and steps should all be nested under the build job in proper YAML structure.
• You have a standalone docker build step before the build-push-action, which duplicates work—consider merging it into the Buildx build/push step for consistency.
• Using a timestamp for tagging makes builds non-reproducible; consider leveraging the metadata-action tags or commit SHA for deterministic image versions.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The jobs.build section looks mis-indented—runs-on, permissions, and steps should all be nested under the build job in proper YAML structure.
- You have a standalone `docker build` step before the build-push-action, which duplicates work—consider merging it into the Buildx build/push step for consistency.
- Using a timestamp for tagging makes builds non-reproducible; consider leveraging the metadata-action tags or commit SHA for deterministic image versions.

## Individual Comments

### Comment 1
<location> `.github/workflows/docker.yml:26-27` </location>
<code_context>
-
-jobs:
-
-  build:
-
-    runs-on: ubuntu-latest
-
-    steps:
-    - uses: actions/checkout@v4
-    - name: Build the Docker image
-      run: docker build . --file Dockerfile --tag my-image-name:${{ github.sha }}
</code_context>

<issue_to_address>
**issue (bug_risk):** Job syntax is invalid; steps are defined before 'runs-on'.

Please move 'runs-on' above 'steps' and ensure all steps are correctly nested under the job.
</issue_to_address>

### Comment 2
<location> `.github/workflows/docker.yml:28` </location>
<code_context>
+jobs:
+  build:
+    - name: Build the Docker image
+      run: docker build . --file path/to/Dockerfile --tag my-image-name:$(date +%s)
+
+  runs-on: ubuntu-latest
</code_context>

<issue_to_address>
**suggestion:** Direct shell command for Docker build is redundant and misplaced.

This step duplicates the build already handled by build-push-action and may lead to inconsistent configurations or caching. Please remove it.
</issue_to_address>

### Comment 3
<location> `.github/workflows/docker.yml:100` </location>
<code_context>
+          DIGEST: ${{ steps.build-and-push.outputs.digest }}
+        # This step uses the identity token to provision an ephemeral certificate
+        # against the sigstore community Fulcio instance.
+        run: echo "${TAGS}" | xargs -I {} cosign sign --yes {}@${DIGEST}
</code_context>

<issue_to_address>
**suggestion:** Cosign signing step may fail if TAGS is empty or malformed.

Add validation to ensure TAGS is set and contains valid values before running the signing step.
</issue_to_address>

---

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.}