Skip to content

Added migrate image to public registry#756

Merged
rmgpinto merged 1 commit intomainfrom
push-migrate-public-registry
May 29, 2025
Merged

Added migrate image to public registry#756
rmgpinto merged 1 commit intomainfrom
push-migrate-public-registry

Conversation

@rmgpinto
Copy link
Copy Markdown
Collaborator

ref https://linear.app/ghost/issue/PROD-1662

  • Added migrate image to public registry

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 29, 2025

Warning

Rate limit exceeded

@rmgpinto has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 18 minutes and 19 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.

📥 Commits

Reviewing files that changed from the base of the PR and between d3bf1d6 and 9a1ff2a.

📒 Files selected for processing (1)
  • .github/workflows/cicd.yml (3 hunks)

"""

Walkthrough

This change updates the CI/CD workflow configuration in .github/workflows/cicd.yml by introducing new steps to handle Docker image management for the migrations image. Specifically, it adds steps to generate Docker metadata and push the migrations Docker image to the public GitHub Container Registry (ghcr.io), mirroring the tagging and labeling approach used for existing ActivityPub images. The step for pushing to the public registry currently lacks an active branch restriction. Additionally, the step for pushing to the private Google Artifact Registry has been renamed for clarity. No application code or exported entities were modified.

Possibly related PRs

  • Added push step to the future main registry #406: Modifies GitHub Actions workflows to enhance Docker image metadata handling and pushing steps for the migrations image, similar to the main PR's addition of public registry support.
  • Fixed cicd deploy pipeline #537: Adjusts CI/CD workflow steps for migrations Docker image tagging, pushing, and conditional execution, closely related to this PR’s workflow modifications.
  • Updated GCP registry tags #465: Adjusts Docker metadata tags for ActivityPub and Migrations images in CI workflows, relating to the main PR's changes in tagging and pushing Docker images.

Suggested labels

ricardo.ghost.is
"""


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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Copy Markdown

@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: 2

🧹 Nitpick comments (1)
.github/workflows/cicd.yml (1)

105-125: Update labels to reflect migrations image
The metadata labels for the migrations image still use generic ActivityPub labels, which can be confusing. Consider updating the org.opencontainers.image.title and org.opencontainers.image.description to reference “Migrations” explicitly.

@@ -118,2 +118,2
-            org.opencontainers.image.title=Ghost — ActivityPub
-            org.opencontainers.image.description=Federate your Ghost site with ActivityPub to join the world's largest open network.
+            org.opencontainers.image.title=Ghost — ActivityPub Migrations
+            org.opencontainers.image.description=Database migrations image for Ghost — ActivityPub.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 50b903c and 7a63125.

📒 Files selected for processing (1)
  • .github/workflows/cicd.yml (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Build, Test and Push

Comment thread .github/workflows/cicd.yml
Comment on lines +205 to 211
- name: "Push Migrations Docker image to private registry"
if: github.ref == 'refs/heads/main' || (github.event_name == 'pull_request' && (github.event.action == 'opened' || github.event.action == 'synchronize' || github.event.action == 'reopened' || github.event.action == 'labeled' || github.event.action == 'unlabeled'))
uses: docker/build-push-action@v6
with:
context: migrate
push: true
tags: ${{ steps.migrations-docker-metadata.outputs.tags }}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Include labels for private migrations image push
The private registry push step omits the labels output from metadata, resulting in unlabeled images. Add the labels (and optionally platforms) to keep consistency with other push steps.

@@ -209,3 +209,5
           push: true
           tags: ${{ steps.migrations-docker-metadata.outputs.tags }}
+          labels: ${{ steps.migrations-docker-metadata.outputs.labels }}
+          platforms: linux/amd64
📝 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: "Push Migrations Docker image to private registry"
if: github.ref == 'refs/heads/main' || (github.event_name == 'pull_request' && (github.event.action == 'opened' || github.event.action == 'synchronize' || github.event.action == 'reopened' || github.event.action == 'labeled' || github.event.action == 'unlabeled'))
uses: docker/build-push-action@v6
with:
context: migrate
push: true
tags: ${{ steps.migrations-docker-metadata.outputs.tags }}
- name: "Push Migrations Docker image to private registry"
if: github.ref == 'refs/heads/main' || (github.event_name == 'pull_request' && (github.event.action == 'opened' || github.event.action == 'synchronize' || github.event.action == 'reopened' || github.event.action == 'labeled' || github.event.action == 'unlabeled'))
uses: docker/build-push-action@v6
with:
context: migrate
push: true
tags: ${{ steps.migrations-docker-metadata.outputs.tags }}
labels: ${{ steps.migrations-docker-metadata.outputs.labels }}
platforms: linux/amd64
🤖 Prompt for AI Agents
In .github/workflows/cicd.yml around lines 205 to 212, the step pushing the
migrations Docker image to the private registry is missing the inclusion of
labels from the metadata output. To fix this, add the labels field using the
appropriate output from the metadata step, and optionally include platforms to
match other push steps. This ensures the pushed image is properly labeled and
consistent with other images.

@rmgpinto rmgpinto force-pushed the push-migrate-public-registry branch from d3bf1d6 to 9a1ff2a Compare May 29, 2025 13:39
@rmgpinto rmgpinto enabled auto-merge (squash) May 29, 2025 13:40
@rmgpinto rmgpinto merged commit 089ee7f into main May 29, 2025
9 checks passed
@rmgpinto rmgpinto deleted the push-migrate-public-registry branch May 29, 2025 13:49
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