Skip to content

fixed wrong tag used in docker-compose.yml#142

Open
rotarymars wants to merge 2 commits intomainfrom
fix/docker-tag
Open

fixed wrong tag used in docker-compose.yml#142
rotarymars wants to merge 2 commits intomainfrom
fix/docker-tag

Conversation

@rotarymars
Copy link
Member

@rotarymars rotarymars commented Mar 1, 2026

It looks like I have forgotten to fix the temporary changes that I've made before and pushed, and unfortunately merged into the main branch.

Description

Fixes the tag used on docker-compose.yml

Type of Change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to change)
  • 📝 Documentation update
  • 🎨 Style/UI change
  • ♻️ Refactor (no functional changes)
  • 🔧 Configuration change

Changes Made

  • Rewrite the tag

Testing

  • Tested locally with npm run dev
  • Build passes (npm run build)
  • Lint passes (npm run lint)

Screenshots (if applicable)

Checklist

  • My code follows the project's coding style
  • I have performed a self-review of my code
  • I have commented my code where necessary
  • My changes generate no new warnings
  • Any dependent changes have been merged and published

Related Issues

Summary by CodeRabbit

  • Chores
    • Updated deployment images to use the main release instead of the prior build tag.
    • Fixed service naming in deployment scripts to ensure the correct service is started.

It looks like I have forgotten to fix the temporary changes
that I've made before and pushed, and unfortunately merged
into the main branch.
Copilot AI review requested due to automatic review settings March 1, 2026 12:22
@vercel
Copy link

vercel bot commented Mar 1, 2026

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

Project Deployment Actions Updated (UTC)
kss-it-committee-github-io Ready Ready Preview, Comment Mar 3, 2026 5:12am

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 1, 2026

📝 Walkthrough

Walkthrough

Updates Docker Compose image tags for nextjs-dev and nextjs-prod from pr-131 to main, and corrects the service name reference in prod.sh from next.js-prod to nextjs-prod.

Changes

Cohort / File(s) Summary
Compose image updates
docker-compose.yml
Changed images for nextjs-dev and nextjs-prod from ghcr.io/...:pr-131 to ghcr.io/...:main. No other compose keys modified.
Startup script fix
prod.sh
Renamed service reference from next.js-prod to nextjs-prod in the start command; no other logic changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

  • mochi-k18
  • katsumata68
  • hatuna-827

Poem

🐰 I hopped from pr-131 to main with cheer,
Tags refreshed, the containers draw near.
A dot removed, a name made right,
We sprint to prod beneath moonlight. 🥕🐇

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'fixed wrong tag used in docker-compose.yml' accurately reflects the main change: updating Docker image tags from pr-131 to main in docker-compose.yml, plus a service name correction in prod.sh.
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 docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/docker-tag

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.


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
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the Docker Compose configuration to stop referencing a temporary PR-specific image tag and instead pull images associated with the main branch.

Changes:

  • Update nextjs-dev image tag from pr-131 to main
  • Update nextjs-prod image tag from pr-131 to main

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link
Contributor

@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

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@prod.sh`:
- Line 1: prod.sh is executable but missing a shebang so invoking ./prod.sh can
run under an unintended shell; edit prod.sh and insert an explicit interpreter
declaration as the very first line (for example, use /usr/bin/env bash) so the
script always runs with the intended shell, then keep the executable bit set and
verify execution with ./prod.sh.

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 68cf009 and 257ec57.

📒 Files selected for processing (1)
  • prod.sh

@@ -1 +1 @@
docker compose up next.js-prod
docker compose up nextjs-prod
Copy link
Contributor

@coderabbitai coderabbitai bot Mar 3, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

fd '^prod\.sh$' --type f

Repository: KSS-IT-Committee/KSS-IT-Committee.github.io

Length of output: 94


🏁 Script executed:

find . -name 'prod.sh' -type f -exec head -n 5 {} +

Repository: KSS-IT-Committee/KSS-IT-Committee.github.io

Length of output: 116


🏁 Script executed:

fd '\.sh$' --type f -exec head -n 1 {} + | head -20

Repository: KSS-IT-Committee/KSS-IT-Committee.github.io

Length of output: 317


🏁 Script executed:

rg -l "prod\.sh" --type md --type json --type yaml

Repository: KSS-IT-Committee/KSS-IT-Committee.github.io

Length of output: 69


🏁 Script executed:

fd '\.sh$' --type f

Repository: KSS-IT-Committee/KSS-IT-Committee.github.io

Length of output: 119


🏁 Script executed:

cat package.json | grep -A 10 -B 2 '"scripts"'

Repository: KSS-IT-Committee/KSS-IT-Committee.github.io

Length of output: 401


🏁 Script executed:

rg "prod\.sh" --type sh --type dockerfile --type makefile --type json

Repository: KSS-IT-Committee/KSS-IT-Committee.github.io

Length of output: 121


🏁 Script executed:

cat dev.sh

Repository: KSS-IT-Committee/KSS-IT-Committee.github.io

Length of output: 115


🏁 Script executed:

cat deploy-rolling.sh

Repository: KSS-IT-Committee/KSS-IT-Committee.github.io

Length of output: 2679


🏁 Script executed:

ls -la *.sh

Repository: KSS-IT-Committee/KSS-IT-Committee.github.io

Length of output: 266


Add an explicit shebang to the executable script.

prod.sh is marked as executable but lacks a shebang. Running ./prod.sh without one can fail or use an unintended shell. Add an explicit interpreter declaration at the top.

Proposed fix
+#!/usr/bin/env bash
+
 docker compose up nextjs-prod
📝 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
docker compose up nextjs-prod
#!/usr/bin/env bash
docker compose up nextjs-prod
🧰 Tools
🪛 Shellcheck (0.11.0)

[error] 1-1: Tips depend on target shell and yours is unknown. Add a shebang or a 'shell' directive.

(SC2148)

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

In `@prod.sh` at line 1, prod.sh is executable but missing a shebang so invoking
./prod.sh can run under an unintended shell; edit prod.sh and insert an explicit
interpreter declaration as the very first line (for example, use /usr/bin/env
bash) so the script always runs with the intended shell, then keep the
executable bit set and verify execution with ./prod.sh.

Copy link
Member Author

Choose a reason for hiding this comment

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

Is this still true?

Copy link
Contributor

Choose a reason for hiding this comment

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

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
cat prod.sh

Length of output: 29


@rotarymars, yes, the concern is still valid. The current prod.sh still has no shebang:

docker compose up nextjs-prod

Adding #!/usr/bin/env bash as the first line is still recommended to ensure the script always runs with the intended shell:

+#!/usr/bin/env bash
+
 docker compose up nextjs-prod

@rotarymars
Copy link
Member Author

(m_m)

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.

6 participants