Skip to content

Conversation

@smoshiur1237
Copy link
Contributor

Some additional info and example to ease future release work

@k8s-ci-robot k8s-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Dec 3, 2025
@netlify
Copy link

netlify bot commented Dec 3, 2025

Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!

Name Link
🔨 Latest commit 0d868a8
🔍 Latest deploy log https://app.netlify.com/projects/kubernetes-sigs-cluster-api-openstack/deploys/6931660bd58e4a00086959f0
😎 Deploy Preview https://deploy-preview-2878--kubernetes-sigs-cluster-api-openstack.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Dec 3, 2025
RELEASE.md Outdated
-`git push -u origin release-notes-X.Y.Z`
- Important! The commit should only contain the release notes file, nothing
else, otherwise automation will not work.
- Important! The `origin` must be directed to the fork (for example: nordix) otherwise it will have error. Also, the commit should only contain
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's keep the most important first. Pushing through the fork is normal flow and should not be surprising. Also, maintainers can push directly to upstream (but it is better to go through the fork, since any branch in upstream will get branch protections).

Suggested change
- Important! The `origin` must be directed to the fork (for example: nordix) otherwise it will have error. Also, the commit should only contain
- Important! The commit should only contain the release notes file, nothing
else, otherwise automation will not work. Push as normal, through your fork (`origin`).

Signed-off-by: smoshiur1237 <moshiur.rahman@est.tech>
@smoshiur1237 smoshiur1237 force-pushed the update-release-doc-moshiur branch from 09f9df3 to 0d868a8 Compare December 4, 2025 10:44
@smoshiur1237 smoshiur1237 requested a review from lentzi90 December 4, 2025 10:45
@smoshiur1237
Copy link
Contributor Author

/cc @bnallapeta @lentzi90

Copy link
Contributor

@lentzi90 lentzi90 left a comment

Choose a reason for hiding this comment

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

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lentzi90

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 4, 2025
@bnallapeta
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 4, 2025
@k8s-ci-robot k8s-ci-robot merged commit de34a9f into kubernetes-sigs:main Dec 4, 2025
13 checks passed
@github-project-automation github-project-automation bot moved this from Inbox to Done in CAPO Roadmap Dec 4, 2025
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants