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.

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

feat: allow specifying custom release-plz source for testing #148

Closed

Conversation

zvolin
Copy link

@zvolin zvolin commented Jun 9, 2024

This allows specifying custom repository url and branch of the release-plz used by the action. If set, instead of fetching the release version with install action, it will clone the specified repository and build the tool locally.
It's likely that you have better ways of testing the release-plz changes that I'm not aware of, but in case not, I found this pretty useful.

example usage
example run

@zvolin zvolin force-pushed the feat/custom-release-plz-for-tests branch from 0570a1c to 7ff0a56 Compare June 9, 2024 19:13
@marcoieni
Copy link
Member

Im not too sure this is useful.
Cargo install already has an option to install from git.
So imo if you are already forking the extension you might just use this instead of specifying the options in the action

@marcoieni marcoieni closed this Jul 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants