-
Notifications
You must be signed in to change notification settings - Fork 58
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
clarify release/pre_release in README #100
Conversation
#95 Signed-off-by: Aidan Oldershaw <aoldershaw@pivotal.io>
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.
I think it looks good the way it is, I just had some comments that might or might not make it a little better.
README.md
Outdated
also set to `false`). If `false`, only non-prerelease releases will be detected | ||
and published. | ||
**note:** if both `release` and `pre_release` are set to `true`, `put` | ||
produces final releases and `check` detects both pre-releases and releases. |
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.
I didn't notice in the beginning that this is a different note, do you think it would be better to have both notes in the same place?
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.
Ah good point catch - I was hoping they'd appear on separate lines
I put line breaks between the notes and the body - let me know what you think
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.
when I read my comment again I noticed it is very vague 😁.
what I meant is to have all the notes related different setups in the same place, I will add it as a suggestion.
* space out notes * add link for semver compliant Signed-off-by: Aidan Oldershaw <aoldershaw@pivotal.io>
Signed-off-by: Aidan Oldershaw <aoldershaw@pivotal.io>
README.md
Outdated
**note:** if both `release` and `pre_release` are set to `false`, `put` will | ||
still produce final releases | ||
**note:** releases must have [semver compliant](https://semver.org/#backusnaur-form-grammar-for-valid-semver-versions) tags to be detected. |
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.
**note:** if both `release` and `pre_release` are set to `false`, `put` will | |
still produce final releases | |
**note:** releases must have [semver compliant](https://semver.org/#backusnaur-form-grammar-for-valid-semver-versions) tags to be detected. |
Signed-off-by: Aidan Oldershaw <aoldershaw@pivotal.io>
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.
Thanks for addressing the comments 😃.
closes #95
Signed-off-by: Aidan Oldershaw aoldershaw@pivotal.io