Skip to content
This repository has been archived by the owner on Aug 29, 2020. It is now read-only.

Fail if issues are not closed #29

Open
distantcam opened this issue Jan 25, 2016 · 1 comment
Open

Fail if issues are not closed #29

distantcam opened this issue Jan 25, 2016 · 1 comment

Comments

@distantcam
Copy link
Contributor

As part of generating a release, all the issues for the milestone should be closed. If they are not, throw.

This is the same as if an issue for the milestone doesn't have the correct labels.

@gep13
Copy link

gep13 commented Jan 26, 2016

@distantcam this is interesting. I had a similar suggestion made on GitReleaseManager (a hard fork of GitHubReleaseNotes) where the suggestion was to move any unclosed issues to the next/new milestone:

GitTools/GitReleaseManager#55

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants