Correct ram-size parameter examples: remove 'M' suffix to show proper format #450
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 corrects the documentation for the
ram-size
parameter in both the README.md and action.yml files by updating the example format.Problem
The
ram-size
parameter documentation showed an inconsistent example format:e.g. 2048M
This suggested users should include the unit suffix in the parameter value, but the correct format expects just the numeric value.
Solution
Updated the examples in both files:
e.g. 2048M
toe.g. 2048
e.g. 2048M
toe.g. 2048
The descriptive text about "denoted with K or M" remains unchanged to help users understand the unit notation, while the examples now show the correct parameter format that the action expects.