-
Notifications
You must be signed in to change notification settings - Fork 10
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.
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
Adopt same release automation as used by main project (the robot etc) #425
Conversation
f89dc93
to
2931f7d
Compare
Signed-off-by: kwall <[email protected]>
c7dfe03
to
2135dc7
Compare
@SamBarker @robobario I've given this a spin on my own fork: stage release then drop the release. The the pieces seem to be functioning as expected. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM once the little bits are fixed up
Signed-off-by: Keith Wall <[email protected]>
7d4858c
to
a3cfd64
Compare
Quality Gate passedIssues Measures |
Type of change
Select the type of your PR
Description
Update release automation used by the project to match that of the main repo.
Approach: I've literally copied/pasted the files, removing the parts responsible for documentation and update the repo name from
kroxylicious
->kroxylicious-junit5-extension
.Additional Context
Why are you making this pull request?
Checklist
Please go through this checklist and make sure all applicable tasks have been done