mirror of https://github.com/kubevela/kubevela.git synced 2026-05-21 08:43:35 +00:00

Files

jguionnet 05b0ec89a5

Webhook Upgrade Validation / webhook-upgrade-check (push) Failing after 25s

Refactor: Update documentation generation to retain .md extensions and fixed Components header (#6957 )

- Modified the documentation generation logic to keep .md file extensions, enhancing IDE support and compatibility with Docusaurus.
- Updated various documentation headers to include the correct .md references in auto-generated messages, ensuring consistency across multiple components (component, policy, trait, workflow).

Signed-off-by: jguionnet jguionnet@guidewire.com

Signed-off-by: jguionnet jguionnet@guidewire.com
Signed-off-by: Jerome Guionnet <jguionnet@guidewire.com>

2025-10-22 18:17:46 -07:00

component

Feat: added support for stateful set (#6638 )

2025-04-12 07:17:21 +08:00

policy

Chore: remove legacy rollout and scope (#6068 )

2023-06-05 10:57:38 +08:00

trait

Refactor: Update documentation generation to retain .md extensions and fixed Components header (#6957 )

2025-10-22 18:17:46 -07:00

workflowstep

Feat: apply-component supports namespace (#6248 )

2023-08-31 14:08:48 +08:00

README.md

Chore: update description of policy/workflowstep definition (#4428 )

2022-07-25 10:34:26 +08:00

README.md

Why do the def-doc embedded here instead of inside the kubevela.io?

The example can be used not only in generation the reference doc of kubevela.io, but also help users to generate their own by vela show.
They're examples usage of built-in definitions, they should align with the built-in definitions files.