Skip to content

Staging#70

Merged
Shashank0701-byte merged 6 commits intomainfrom
staging
Mar 11, 2026
Merged

Staging#70
Shashank0701-byte merged 6 commits intomainfrom
staging

Conversation

@Shashank0701-byte
Copy link
Owner

@Shashank0701-byte Shashank0701-byte commented Mar 11, 2026

Summary by CodeRabbit

  • Chores
    • Docker images are now built and automatically published to the GitHub Container Registry for non‑PR commits.
    • Builds for pull requests are optimized to skip pushing images.
    • Docker image naming/tagging updated to the registry-qualified format.
    • CI now authenticates with the container registry during the build to enable secure publishing.

@vercel
Copy link

vercel bot commented Mar 11, 2026

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

Project Deployment Actions Updated (UTC)
system-craft Ready Ready Preview, Comment Mar 11, 2026 3:10pm

@coderabbitai
Copy link

coderabbitai bot commented Mar 11, 2026

Warning

Rate limit exceeded

@Shashank0701-byte has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 7 minutes and 27 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7c822a4d-bff6-4031-b01f-b21f1b7a4a6b

📥 Commits

Reviewing files that changed from the base of the PR and between 81fad31 and 17fd613.

📒 Files selected for processing (1)
  • .github/workflows/ci.yml
📝 Walkthrough

Walkthrough

GitHub Actions workflow updated to authenticate to ghcr.io, add packages: write permission, conditionally push Docker images except for pull requests, and change image tags to the GitHub Container Registry path.

Changes

Cohort / File(s) Summary
CI Workflow / Docker Registry
.github/workflows/ci.yml
Added top-level packages: write permission; added docker/login-action@v3 step (registry: ghcr.io, username: ${{ github.actor }}, password: ${{ secrets.GITHUB_TOKEN }}); moved login before buildx; changed Build step to push: ${{ github.event_name != 'pull_request' }} and tag to ghcr.io/${{ github.repository }}/systemcraft-web:latest.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 I hopped into CI with glee,
Pushed my image to ghcr.io’s sea,
A token, a login, a ready tag,
Skip the PRs, let pushes wag,
Builds now hum — hooray for me! 🎩

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Staging' is vague and does not convey meaningful information about the changeset, which involves configuring Docker image builds and publishing to GitHub Container Registry. Consider a more descriptive title such as 'Configure Docker image publishing to GHCR' or 'Add Docker login and GHCR push configuration' to clearly communicate the primary change.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch staging

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (2)
.github/workflows/ci.yml (2)

55-56: Consider adding versioned tags for better traceability.

Using only latest makes it difficult to track which commit is deployed and to rollback to specific versions. Consider adding a SHA-based or ref-based tag alongside latest.

♻️ Suggested improvement
-          tags: ghcr.io/${{ github.repository }}/systemcraft-web:latest
+          tags: |
+            ghcr.io/${{ github.repository }}/systemcraft-web:latest
+            ghcr.io/${{ github.repository }}/systemcraft-web:${{ github.sha }}
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/ci.yml around lines 55 - 56, The current workflow only
pushes a single `tags: ghcr.io/${{ github.repository }}/systemcraft-web:latest`
which prevents traceability; update the push tags so you push multiple tags
including a commit SHA and/or ref name alongside `latest` (e.g., add
`ghcr.io/${{ github.repository }}/systemcraft-web:${{ github.sha }}` and/or
`ghcr.io/${{ github.repository }}/systemcraft-web:${{ github.ref_name }}`) so
that the `tags` entry for the push step contains both the `:latest` and at least
one versioned tag to enable rollbacks and clear mapping from image to
commit/ref.

11-11: Minor typo: "Registery" → "Registry".

The permission itself is correct for pushing to ghcr.io.

✏️ Suggested fix
-  packages: write  # --> Allows Github Actions to upload to the Container Registery
+  packages: write  # --> Allows GitHub Actions to upload to the Container Registry
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/ci.yml at line 11, The comment containing the typo
"Registery" should be corrected to "Registry" on the line that documents the
packages permission (the comment following "packages: write"); update only the
comment text to "Allows Github Actions to upload to the Container Registry" and
keep "packages: write" unchanged so the permission remains correct.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/ci.yml:
- Around line 41-46: Fix the YAML indentation and spelling in the CI job step
titled "Login to Container Registery": align the `uses: docker/login-action@v3`
and its `with:` block to the same indentation level as `name:` (two spaces after
the `-`) so the step keys are at the same mapping level, and rename `Login to
Container Registery` to `Login to Container Registry`; ensure `registry:`,
`username:`, and `password:` remain under `with:` with correct indentation.

---

Nitpick comments:
In @.github/workflows/ci.yml:
- Around line 55-56: The current workflow only pushes a single `tags:
ghcr.io/${{ github.repository }}/systemcraft-web:latest` which prevents
traceability; update the push tags so you push multiple tags including a commit
SHA and/or ref name alongside `latest` (e.g., add `ghcr.io/${{ github.repository
}}/systemcraft-web:${{ github.sha }}` and/or `ghcr.io/${{ github.repository
}}/systemcraft-web:${{ github.ref_name }}`) so that the `tags` entry for the
push step contains both the `:latest` and at least one versioned tag to enable
rollbacks and clear mapping from image to commit/ref.
- Line 11: The comment containing the typo "Registery" should be corrected to
"Registry" on the line that documents the packages permission (the comment
following "packages: write"); update only the comment text to "Allows Github
Actions to upload to the Container Registry" and keep "packages: write"
unchanged so the permission remains correct.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 847bface-af86-411d-a011-4808c1ea86b3

📥 Commits

Reviewing files that changed from the base of the PR and between 6969a9f and fabba51.

📒 Files selected for processing (1)
  • .github/workflows/ci.yml

Comment on lines +41 to +46
- name: Login to Container Registery
uses: docker/login-action@v3
with:
registry: ghcr.io
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

Critical: YAML syntax error due to incorrect indentation.

The uses: and with: block have excessive indentation. They should align with name: (2 spaces from the -). This will cause the workflow to fail to parse.

Also, "Registery" should be "Registry".

🐛 Proposed fix
-      - name: Login to Container Registery
-              uses: docker/login-action@v3
-              with:
-                registry: ghcr.io
-                username: ${{ github.actor }}
-                password: ${{ secrets.GITHUB_TOKEN }}
+      - name: Login to Container Registry
+        uses: docker/login-action@v3
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: Login to Container Registery
uses: docker/login-action@v3
with:
registry: ghcr.io
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
- name: Login to Container Registry
uses: docker/login-action@v3
with:
registry: ghcr.io
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
🧰 Tools
🪛 actionlint (1.7.11)

[error] 42-42: could not parse as YAML: mapping values are not allowed in this context

(syntax-check)

🪛 YAMLlint (1.38.0)

[error] 42-42: syntax error: mapping values are not allowed here

(syntax)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/ci.yml around lines 41 - 46, Fix the YAML indentation and
spelling in the CI job step titled "Login to Container Registery": align the
`uses: docker/login-action@v3` and its `with:` block to the same indentation
level as `name:` (two spaces after the `-`) so the step keys are at the same
mapping level, and rename `Login to Container Registery` to `Login to Container
Registry`; ensure `registry:`, `username:`, and `password:` remain under `with:`
with correct indentation.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

♻️ Duplicate comments (1)
.github/workflows/ci.yml (1)

11-11: ⚠️ Potential issue | 🟡 Minor

Typo: "Registery" should be "Registry".

The comment contains a spelling error.

📝 Proposed fix
-  packages: write  # --> Allows Github Actions to upload to the Container Registery
+  packages: write  # --> Allows GitHub Actions to upload to the Container Registry
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/ci.yml at line 11, Update the inline comment on the CI
workflow line containing "packages: write  # --> Allows Github Actions to upload
to the Container Registery" and correct the typo by replacing "Registery" with
"Registry" so the comment reads "...upload to the Container Registry"; ensure
the change is made next to the "packages: write" entry in the
.github/workflows/ci.yml file.
🧹 Nitpick comments (1)
.github/workflows/ci.yml (1)

55-56: Consider adding a commit SHA tag for version traceability.

Using only latest makes it difficult to track which commit is deployed. Adding the commit SHA as an additional tag improves rollback capability and debugging.

♻️ Proposed enhancement
          push: ${{ github.event_name != 'pull_request' }}
-          tags: ghcr.io/${{ github.repository }}/systemcraft-web:latest
+          tags: |
+            ghcr.io/${{ github.repository }}/systemcraft-web:latest
+            ghcr.io/${{ github.repository }}/systemcraft-web:${{ github.sha }}
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/ci.yml around lines 55 - 56, The workflow currently pushes
only the "latest" image tag (see the tags line), which hinders traceability;
update the workflow to add an additional image tag using the commit SHA (e.g.,
use the GitHub Actions variable github.sha or github.ref_short) alongside
ghcr.io/${{ github.repository }}/systemcraft-web:latest so each push also tags
ghcr.io/${{ github.repository }}/systemcraft-web:<commit-sha>, ensuring both
tags are pushed during the same push/publish step.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In @.github/workflows/ci.yml:
- Line 11: Update the inline comment on the CI workflow line containing
"packages: write  # --> Allows Github Actions to upload to the Container
Registery" and correct the typo by replacing "Registery" with "Registry" so the
comment reads "...upload to the Container Registry"; ensure the change is made
next to the "packages: write" entry in the .github/workflows/ci.yml file.

---

Nitpick comments:
In @.github/workflows/ci.yml:
- Around line 55-56: The workflow currently pushes only the "latest" image tag
(see the tags line), which hinders traceability; update the workflow to add an
additional image tag using the commit SHA (e.g., use the GitHub Actions variable
github.sha or github.ref_short) alongside ghcr.io/${{ github.repository
}}/systemcraft-web:latest so each push also tags ghcr.io/${{ github.repository
}}/systemcraft-web:<commit-sha>, ensuring both tags are pushed during the same
push/publish step.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9dd91a27-0480-49ec-8773-c12e8357d885

📥 Commits

Reviewing files that changed from the base of the PR and between fabba51 and 81fad31.

📒 Files selected for processing (1)
  • .github/workflows/ci.yml

fix: force lowercase docker tags in ci workflow
@Shashank0701-byte Shashank0701-byte merged commit 14baeee into main Mar 11, 2026
5 checks passed
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