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.

Sign up for GitHub

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

Jump to bottom

Marks repo as ready for release when non-semver tags exist #6

Open
bergren2 opened this issue Jun 12, 2018 · 2 comments
Open

Marks repo as ready for release when non-semver tags exist #6

bergren2 opened this issue Jun 12, 2018 · 2 comments

Comments

@bergren2
Copy link
Member

Noticed an issue when there are a list of semver tags that exist IN ADDITION to non-semver tags that appear after the latest semver tag.
@rehret
Copy link
Collaborator

rehret commented Jun 25, 2018

What's the use case for this? Why wouldn't a new semver tag at the target commit work? I can picture scenarios when a non-semver tag is added which shouldn't be considered for release. For example, 1.1.0-rc.

@rehret
Copy link
Collaborator

rehret commented Jun 28, 2018

I've re-read this issue and maybe I misunderstood it. Can I get some more information?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bergren2 @rehret