Skip to content

add overview explanation about how CI/CD github workflow works. - #805

Merged
kubeedge-bot merged 2 commits into
kubeedge:masterfrom
fujitatomoya:add-ci-cd-explanation
Sep 1, 2026
Merged

add overview explanation about how CI/CD github workflow works.#805
kubeedge-bot merged 2 commits into
kubeedge:masterfrom
fujitatomoya:add-ci-cd-explanation

Conversation

@fujitatomoya

@fujitatomoya fujitatomoya commented Jun 1, 2026

Copy link
Copy Markdown
Contributor
  • Please check if the PR fulfills these requirements
  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

Which issue(s) this PR fixes:

Fixes #

  • What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

It simply adds the overview explanation how github workflow goes in kubeedge project.

  • What is the current behavior? (You can also link to an open issue here)

No documentation available.

  • What is the new behavior (if this is a feature change)?

Overview is explained.

  • Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

No

  • Other information:

@kubeedge-bot kubeedge-bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jun 1, 2026

@gemini-code-assist gemini-code-assist 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.

Code Review

This pull request introduces a new developer documentation file (docs/developer/ci_cd.md) that comprehensively details the CI/CD workflows for KubeEdge, including core CI, docs-only CI, code quality, security, scheduled compatibility tests, and release workflows. The review feedback points out a typo in the job name release-assests which should be corrected to release-assets.

Comment thread docs/developer/ci_cd.md Outdated

@fujitatomoya fujitatomoya left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

doc build is supposed to fail because of #804. we need to rebase this against it.

@fujitatomoya
fujitatomoya force-pushed the add-ci-cd-explanation branch from 9638d36 to e20515c Compare June 15, 2026 23:14
@fujitatomoya

Copy link
Copy Markdown
Contributor Author

@kevin-wangzefeng this should also pass now.

Signed-off-by: Tomoya Fujita <[email protected]>

@Shelley-BaoYue Shelley-BaoYue left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

👍
/lgtm
/approve

@kubeedge-bot kubeedge-bot added the lgtm Indicates that a PR is ready to be merged. label Sep 1, 2026
@kubeedge-bot

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Shelley-BaoYue

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubeedge-bot kubeedge-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 1, 2026
@kubeedge-bot
kubeedge-bot merged commit 580a9eb into kubeedge:master Sep 1, 2026
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants