Closed khebhut[bot] closed 2 years ago
[APPROVALNOTIFIER] This PR is APPROVED
Approval requirements bypassed by manually added approval.
This pull-request has been approved by: sefkhet-abwy[bot]
The full list of commands accepted by this bot can be found here.
The pull request process is described here
[APPROVALNOTIFIER] This PR is APPROVED
Approval requirements bypassed by manually added approval.
This pull-request has been approved by: sefkhet-abwy[bot]
The full list of commands accepted by this bot can be found here.
The pull request process is described here
[APPROVALNOTIFIER] This PR is APPROVED
Approval requirements bypassed by manually added approval.
This pull-request has been approved by: sefkhet-abwy[bot]
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Hi @khebhut[bot]. Thanks for your PR.
I'm waiting for a thoth-station member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
Hey, @Gkrumbach07!
Opening this PR to create a release in a backwards compatible manner.
IMPORTANT NOTES
If Khebut GitHub App Bot is installed, this issue will trigger a minor release. The bot will open a Pull Request to update the CHANGELOG, fix the opened issue and create a tag.
Only users that are allowed to release (a.k.a. maintainers specified in the .thoth.yaml file) can open the issue, otherwise bot will reject them, commenting and closing the issue. If AICoE CI GitHub App is installed, once the pull request is merged and a new tag is created by the bot, the pipeline to build and push image starts.
WARNING NOTE The release version mentioned in the source-code couldn't be found in git tags, hence the release is created from the start. If that is not the right behavior:
Create a new release issue.
Closes: #9