feat: Add optional fallbackTag input to handle missing latest tags (#52) #54
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NGPixel
approved these changes
Jan 11, 2025
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new optional input parameter, fallbackTag, to address scenarios where no valid latest tag is found in the repository. If provided, the action will use the specified fallback tag as the base for calculating the next version.
Key updates:
Added fallbackTag input to the action configuration.
Updated the logic to check and use the fallback tag if no valid latest tag is available.
Enhanced error handling to ensure graceful fallback or informative error messages.
Updated the README to document the new input parameter and provide usage examples.
This change resolves issue #52