Skip to content

document how to handle the docs when releasing #94

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Sep 23, 2025
Merged

document how to handle the docs when releasing #94

merged 1 commit into from
Sep 23, 2025

Conversation

xrstf
Copy link
Contributor

@xrstf xrstf commented Sep 23, 2025

Summary

I was mega confused because I looked at the wrong workflow. This PR improves our docs to ensure I will remember next time.

What Type of PR Is This?

/kind documentation

Release Notes

NONE

@kcp-ci-bot kcp-ci-bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has signed the DCO. kind/documentation Categorizes issue or PR as related to documentation. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Sep 23, 2025
@xrstf
document how to handle the docs when releasing
cb01a60 
On-behalf-of: @SAP christoph.mewes@sap.com
@xrstf xrstf force-pushed the improve-release-docs branch from 944e2ed to cb01a60 Compare September 23, 2025 08:42
embik
embik approved these changes Sep 23, 2025
View reviewed changes
Copy link
Member

@embik embik left a comment

Choose a reason for hiding this comment

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

/approve

@kcp-ci-bot kcp-ci-bot added the lgtm Indicates that a PR is ready to be merged. label Sep 23, 2025
@kcp-ci-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: embik

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

The pull request process is described here

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

@kcp-ci-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 875d9b2d5bb559f5d8cc8838718bf9711f3319b1

@kcp-ci-bot kcp-ci-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 23, 2025
@kcp-ci-bot kcp-ci-bot merged commit db3f595 into main Sep 23, 2025
10 checks passed
@kcp-ci-bot kcp-ci-bot deleted the improve-release-docs branch September 23, 2025 08:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@embik embik embik approved these changes

Assignees

@embik embik

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has signed the DCO. kind/documentation Categorizes issue or PR as related to documentation. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@xrstf @kcp-ci-bot @embik