195 scopes for dockerlogin action

[hupling]

Description

Short description or comments

Reference

Issues #195

Summary by CodeRabbit

• Chores
  • Enhanced Docker registry login configuration for the image build action by adding push scope settings.
  • Modified Docker image build-and-push workflow to update authentication token configuration while maintaining metadata tagging and push functionality.

[coderabbitai]

📝 Walkthrough

Walkthrough

The GitHub Action's registry login step adds a push scope setting, while the Docker build-and-push step has its GitHub token input commented out, refining the authentication configuration for image building and pushing workflows.

Changes

Cohort / File(s)	Summary
Docker Build Action Configuration action-templates/actions/action-build-image/action.yml	Added scope: "@push" to docker/login-action step and commented out github-token input from docker/build-push-action step.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A scope for pushing, so precise,
The token steps back—a subtle slice,
Registry gates now know the way,
To let the Docker images play! 🐇✨

🚥 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 directly references the main change: adding scopes parameter for Docker login action, which aligns with the changeset that adds 'scope: @push' to the docker/login-action configuration.
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
• Commit unit tests in branch 195-scopes-for-dockerlogin-action

---

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

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

[coderabbitai]

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 `@action-templates/actions/action-build-image/action.yml`:
- Line 68: The commented-out input "github-token: ${{ github.token }}" in
action.yml should be either removed or documented: if it's unused because
authentication is performed by the docker/login-action step, delete that
commented line; otherwise replace the comment with a short explanatory comment
above or inline the line stating why it's disabled and when to re-enable (e.g.,
"disabled because docker/login-action handles auth; enable if using action's
built-in docker auth"), referencing the exact commented token string so
reviewers can find and update the "github-token" entry in action.yml.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 35915a2f-fe56-46d8-bf87-44094762e133

📥 Commits

Reviewing files that changed from the base of the PR and between 9e86471 and 5db7f18.

📒 Files selected for processing (1)

• action-templates/actions/action-build-image/action.yml

[coderabbitai]

🧹 Nitpick | 🔵 Trivial

Remove or document the commented-out code.

Commented code without explanation creates maintenance confusion. Since authentication is already handled by the docker/login-action step, the github-token input is likely unnecessary here.

If intentionally removed: delete the line entirely.
If kept for reference: add a comment explaining why it's disabled and under what circumstances it might be re-enabled.

🧹 Suggested fix: remove the commented line

        tags: ${{ steps.meta.outputs.tags }}
        labels: ${{ steps.meta.outputs.labels }}
-        # github-token: ${{ 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

	# github-token: ${{ github.token }}
	tags: ${{ steps.meta.outputs.tags }}
	labels: ${{ steps.meta.outputs.labels }}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@action-templates/actions/action-build-image/action.yml` at line 68, The
commented-out input "github-token: ${{ github.token }}" in action.yml should be
either removed or documented: if it's unused because authentication is performed
by the docker/login-action step, delete that commented line; otherwise replace
the comment with a short explanatory comment above or inline the line stating
why it's disabled and when to re-enable (e.g., "disabled because
docker/login-action handles auth; enable if using action's built-in docker
auth"), referencing the exact commented token string so reviewers can find and
update the "github-token" entry in action.yml.