Skip to content
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

chore: Update docs to correspond to new release workflow #1326

Merged
merged 2 commits into from
Aug 8, 2024
Merged

chore: Update docs to correspond to new release workflow #1326

merged 2 commits into from
Aug 8, 2024

Conversation

jeffreylimnardy
Copy link
Contributor

Description

Changes proposed in this pull request (what was done and why):

  • Update releasing docs since we moved from prow to GH actions

Changes refer to particular issues, PRs or documents:

Traceability

  • The PR is linked to a GitHub issue.
  • The follow-up issues (if any) are linked in the Related Issues section.
  • If the change is user-facing, the documentation has been adjusted.
  • The feature is unit-tested.
  • The feature is e2e-tested.

@jeffreylimnardy jeffreylimnardy added area/documentation Documentation changes do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/chore Categorizes issue or PR as related to a chore. labels Aug 7, 2024
@kyma-bot
Copy link
Contributor

kyma-bot commented Aug 7, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@kyma-bot kyma-bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cla: yes Indicates the PR's author has signed the CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Aug 7, 2024
@jeffreylimnardy jeffreylimnardy changed the title chore: update docs to correspond to new release workflow chore: Update docs to correspond to new release workflow Aug 7, 2024
@jeffreylimnardy jeffreylimnardy added this to the 1.22.0 milestone Aug 8, 2024
@jeffreylimnardy jeffreylimnardy marked this pull request as ready for review August 8, 2024 06:03
@jeffreylimnardy jeffreylimnardy requested a review from a team as a code owner August 8, 2024 06:03
@kyma-bot kyma-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 8, 2024
@jeffreylimnardy jeffreylimnardy self-assigned this Aug 8, 2024
@kyma-bot kyma-bot added the lgtm Looks good to me! label Aug 8, 2024
@jeffreylimnardy jeffreylimnardy removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 8, 2024
@kyma-bot kyma-bot merged commit 3ea52a0 into kyma-project:main Aug 8, 2024
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mmitoraj mmitoraj mmitoraj approved these changes

Assignees

@mmitoraj mmitoraj

@jeffreylimnardy jeffreylimnardy

Labels
area/documentation Documentation changes cla: yes Indicates the PR's author has signed the CLA. kind/chore Categorizes issue or PR as related to a chore. lgtm Looks good to me! size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Milestone
1.22.0
Development

Successfully merging this pull request may close these issues.
3 participants
@jeffreylimnardy @kyma-bot @mmitoraj