Skip to content

ci: change the docker build trigger condition#163

Merged
GatewayJ merged 1 commit into
rustfs:mainfrom
majinghe:ci/docker-build-trigger
Jul 7, 2026
Merged

ci: change the docker build trigger condition#163
GatewayJ merged 1 commit into
rustfs:mainfrom
majinghe:ci/docker-build-trigger

Conversation

@majinghe

@majinghe majinghe commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator

Type of Change

  • New Feature
  • Bug Fix
  • Documentation
  • Performance Improvement
  • Test/CI
  • Refactor
  • Other:

Related Issues

Summary of Changes

Checklist

  • I have read and followed the CONTRIBUTING.md guidelines
  • Passed make pre-commit (fmt-check + clippy + test + console-lint + console-fmt-check)
  • Added/updated necessary tests
  • Documentation updated (if needed)
  • CHANGELOG.md updated under [Unreleased] (if user-visible change)
  • CI/CD passed (if applicable)

Impact

  • Breaking change (CRD/API compatibility)
  • Requires doc/config/deployment update
  • Other impact:

Verification

make pre-commit

Additional Notes


Thank you for your contribution! Please ensure your PR follows the community standards (CODE_OF_CONDUCT.md) and sign the CLA if this is your first contribution.

@majinghe majinghe requested a review from GatewayJ July 7, 2026 06:58
@GatewayJ GatewayJ added this pull request to the merge queue Jul 7, 2026
Merged via the queue into rustfs:main with commit 5e1b0e9 Jul 7, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bad0d182a3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 18 to +20
workflow_run:
workflows: [ "Continuous Integration" ]
types: [ completed ]
release:
types: [published]

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Put release back at the top-level trigger

For a published release, this workflow does not subscribe to the release event: GitHub Actions documents release and workflow_run as separate top-level events and shows the published-release syntax as on: release: types: [published] (checked GitHub Actions event docs for .github/workflows/docker.yml). Nesting release under workflow_run leaves the Docker publish workflow tied to workflow-run semantics instead of release publishes; the job guard below also only allows workflow_dispatch/workflow_run, so a corrected release trigger must be allowed there or release-published runs will be skipped.

Useful? React with 👍 / 👎.

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.

2 participants