-
-
Notifications
You must be signed in to change notification settings - Fork 471
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
Support custom target_commitish value #76
Conversation
This reverts commit ff30f8e.
I wish it be merged |
Just ran into this problem after naively assuming it would respect the contextual commitish (e.g. |
I've integrated the latest changes from upstream. |
Looks good. Thanks for |
Please can you release this, too? We're keen to get this change into our projects, rather than looking for an alternative. |
@softprops any tentative date for the new release? |
Hello! Also would love for the change to be released. |
Hi @softprops! It looks like this still isn't released. Please can you release it so we can start using the feature? Thanks! |
* Make target_commitish configurable * Store compiled action for testing * Add target_commitish to metadata * Allow override of target_commitish for updating * Print commit usage * Improve message for commit usage * Update draft releases too * Revert "Update draft releases too" This reverts commit ff30f8e. * Integrate latest changes from upstream.
* Make target_commitish configurable * Store compiled action for testing * Add target_commitish to metadata * Allow override of target_commitish for updating * Print commit usage * Improve message for commit usage * Update draft releases too * Revert "Update draft releases too" This reverts commit ff30f8e. * Integrate latest changes from upstream.
* Make target_commitish configurable * Store compiled action for testing * Add target_commitish to metadata * Allow override of target_commitish for updating * Print commit usage * Improve message for commit usage * Update draft releases too * Revert "Update draft releases too" This reverts commit ff30f8e. * Integrate latest changes from upstream.
This PR introduces a new input
target_commitish
.By using this input you can provide a custom value for the commit which is used by the GitHub release.
If this value is not provided, GitHub will use the default branch, see the API documentation.
Now it's possible to provide a specific commit if you create a release without a tag:
I've update the existing tests and added a new test for checking the parsing of the configuration.