Fix Docker Image Build

[gowthamkishore3799]

Summary:

The Docker image pipeline isn’t updating version.txt as expected. This issue is due to the specific steps we use in the pipeline, so I’ve removed the step that pushes code and tags to avoid this problem.

Summary by CodeRabbit

• Chores
  • Updated workflow to set a custom display name for test runs in GitHub Actions.
  • Adjusted Docker publishing workflow to stop pushing tags when updating version information.

[vercel]

@gowthamkishore3799 is attempting to deploy a commit to the Inbox Zero Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

This update modifies two GitHub Actions workflow files. In the Docker build workflow, the tags: true option is removed from the push step, so tags are no longer pushed to the remote. In the test workflow, a run-name attribute is added to set the workflow run's display name.

Changes

File(s)	Change Summary
.github/workflows/build_and_publish_docker.yml	Removed tags: true from the Push changes step in update_version_txt job.
.github/workflows/test.yml	Added run-name: "Run Tests" to set the workflow run display name.

Possibly related PRs

• feat: Add Docker build and publish CI for web app #432: Introduces the Docker build and publish workflow that is modified in this PR.
• Fix: Fix of Docker Image Version Release #434: Refactors and reorganizes the Docker build and version update workflow, related to the same workflow file.

Poem

A bunny hops through YAML fields,
Tweaking tags that version yields.
"Run Tests!" it cries with a cheerful cheer,
As workflows change and clouds clear.
With every push and every name,
The CI dance is never the same! 🐇

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6351fc4 and 8750cde.

📒 Files selected for processing (2)

• .github/workflows/build_and_publish_docker.yml (0 hunks)
• .github/workflows/test.yml (1 hunks)

💤 Files with no reviewable changes (1)

• .github/workflows/build_and_publish_docker.yml

🔇 Additional comments (1)

.github/workflows/test.yml (1)

2-2: Add run-name for clearer workflow run identification.

Introducing the top-level run-name attribute ensures each execution is labeled “Run Tests” in the Actions UI, improving traceability.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[gowthamkishore3799]

Currently the version..txt isnt updated due to the github step we are using which should ideally push tag and along with file which isnt happening

So we are removing tags, which automatically updates the tag push along with file push

[elie222]

So I accepted but ended up reverting. The issue is this:
https://github.com/elie222/inbox-zero/actions/runs/15375444526

The change made in the PR impacts a step after the error.