Closed pseudomuto closed 2 years ago
linux-foundation-easycla[bot]
commented
2 years ago 
The committers listed above are authorized under a signed CLA.
k8s-ci-robot
commented
2 years ago Welcome @pseudomuto!
It looks like this is your first PR to kubernetes-sigs/kubetest2 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.
You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.
You can also check if kubernetes-sigs/kubetest2 has its own contribution guidelines.
You may want to refer to our testing guide if you run into trouble with your tests not passing.
If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!
Thank you, and welcome to Kubernetes. :smiley:
k8s-ci-robot
commented
2 years ago Hi @pseudomuto. Thanks for your PR.
I'm waiting for a kubernetes-sigs 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.
k8s-ci-robot
commented
2 years ago [APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: pseudomuto
To complete the pull request process, please assign bentheelder after the PR has been reviewed.
You can assign the PR to them by writing /assign @bentheelder in a comment when ready.
The full list of commands accepted by this bot can be found here.
MushuEE
commented
2 years ago I don't have any context on this change, was there a conversation in the slack about the need for this framework? @BenTheElder
pseudomuto
commented
2 years ago Ok, thanks for clarifying.
Related: #17
Adding GoReleaser to handle generating releases for tags. This will make it so that cutting releases is as simple as pushing a tag. The result will be a release which includes the changelog, binaries for Linux/Windows/Darwin, as well as the checksums for each of the archives.
To see what this looks like, I've created a dummy release on my fork. Because this is the first release, the changelog is massive, but going forward it should be a little more reasonable.
Sample release: https://github.com/pseudomuto/kubetest2/releases/tag/v0.1.0
I've added some light details about how it works in RELEASE.md as well as the one-time setup step required to make it work (A limited scope GitHub token).