This patch adds milestone capabilities to the tooling. Providers can now be optionally "milestone-aware", meaning they can list, create, and close milestones. Both the GitHub and GitLab providers now implement this functionality.
The functionality drives the following milestone-specific commands:
milestone:list will list milestones associated with the repository.
milestone:create will create a new milestone for the repository, with an optional description.
milestone:close will close a named milestone for the repository, optionally with a specific date.
Additionally, all bump commands and the unreleased:promote command now expose the following options:
--create-milestone will use the newly discovered version or the one provided to the command (e.g., with bump:to-version and unreleased:promote) to create a new milestone.
--create-milestone-with-name NAME will use NAME as a new milestone name to create after doing other options.
This patch adds milestone capabilities to the tooling. Providers can now be optionally "milestone-aware", meaning they can list, create, and close milestones. Both the GitHub and GitLab providers now implement this functionality.
The functionality drives the following milestone-specific commands:
milestone:listwill list milestones associated with the repository.milestone:createwill create a new milestone for the repository, with an optional description.milestone:closewill close a named milestone for the repository, optionally with a specific date.Additionally, all
bumpcommands and theunreleased:promotecommand now expose the following options:--create-milestonewill use the newly discovered version or the one provided to the command (e.g., withbump:to-versionandunreleased:promote) to create a new milestone.--create-milestone-with-name NAMEwill useNAMEas a new milestone name to create after doing other options.Closes #59