You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 3, 2022. It is now read-only.
Currently, associating an issue with a milestone happens based on the milestone's number:
$ ghi open --help
-M, --milestone <n> associate with milestone
This is inconvenient as it usually requires the user to find the milestone number first, and while possible, it is not obvious how to do this via the GitHub interface. It is of course also possible to look up the number via ghi milestone, but this too may not be obvious to many users.
Better would be to support associating an issue with a milestone based on the milestone's name, which the user usually already has in mind, and is in any case easy to remember. #62 already proposed this same improvement, but was closed as the OP never suggested but never actually submitted a pull request. I'm opening a new issue here to see whether the ghi team would be willing to implement this support on their own.
The text was updated successfully, but these errors were encountered:
this would be even better if the milestone assigned would be the first open matching milestone (this would let one have milestones named like '2.0 [4] returning' which would be assigned with a simple:
Currently, associating an issue with a milestone happens based on the milestone's number:
This is inconvenient as it usually requires the user to find the milestone number first, and while possible, it is not obvious how to do this via the GitHub interface. It is of course also possible to look up the number via
ghi milestone
, but this too may not be obvious to many users.Better would be to support associating an issue with a milestone based on the milestone's name, which the user usually already has in mind, and is in any case easy to remember.
#62 already proposed this same improvement, but was closed as the OP never suggested but never actually submitted a pull request. I'm opening a new issue here to see whether the
ghi
team would be willing to implement this support on their own.The text was updated successfully, but these errors were encountered: