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.

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

Insert end date when closing a milestone #568

Closed
AdmiringWorm opened this issue Jan 11, 2024 · 1 comment · Fixed by #614
Closed

Insert end date when closing a milestone #568

AdmiringWorm opened this issue Jan 11, 2024 · 1 comment · Fixed by #614
Labels
Milestone

Comments

@AdmiringWorm
Copy link
Member

Detailed Description

It would be useful for GRM to insert the end/due date of a milestone when closing the milestone issue when a date hasn't already been set.

Context

There are processes some follow to specify the end/due date when closing the milestone, having GRM do this automatically leaves one more thing not needed to be done manually.

Possible Implementation

I am not sure how it is implemented exactly, but it should AFAIK be possible on both GitHub and GitLab.

Your Environment

  • Version Used: 0.16.0
  • Edition Used (.NET Core, .NET Framework): .NET Framework
  • Operating System and version (Windows 10, Ubuntu 18.04): Windows 10
Jericho added a commit to Jericho/GitReleaseManager that referenced this issue Jul 27, 2024
gep13 pushed a commit to Jericho/GitReleaseManager that referenced this issue Jan 9, 2025
Jericho added a commit to Jericho/GitReleaseManager that referenced this issue Feb 1, 2025
gep13 pushed a commit to Jericho/GitReleaseManager that referenced this issue Feb 20, 2025
gep13 pushed a commit to Jericho/GitReleaseManager that referenced this issue Feb 20, 2025
This is controlled via new set-due-date value in the close section of
the GitReleaseManager.yaml file.  This operation is disabled by default,
and something which the user has to opt into to make use of.
@gep13 gep13 added this to the 0.19.0 milestone Feb 20, 2025
gep13 added a commit that referenced this issue Feb 20, 2025
(#568) Set the 'Due date' when closing a milestone if configured to do so
gep13 added a commit that referenced this issue Feb 20, 2025
* release/0.19.0: (44 commits)
  (build) Make use of new GRM features
  (doc) Remove unnecessary space.
  (doc) Document the new set-due-date option
  (doc) Fixed formatting
  (doc) Document the new include-contributors option
  (#89) Add required mappings for GitLab models
  (#89) Include contributors in release notes
  (#568) Set the 'Due date' when closing a milestone
  Bump coverlet.msbuild from 6.0.3 to 6.0.4 in /src in the tests group
  Bump Roslynator.Analyzers
  Bump Shouldly from 4.2.1 to 4.3.0 in /src
  Bump cake-build/cake-action from 2 to 3
  Bump Microsoft.Extensions.DependencyInjection in /src
  Bump NGitLab from 7.1.0 to 7.6.0 in /src
  (build) Install .NET 7.0 on build machine
  Bump NGitLab from 7.0.1 to 7.1.0 in /src
  Bump NUnit3TestAdapter from 4.5.0 to 4.6.0 in /src
  Bump NUnit from 4.1.0 to 4.3.2 in /src
  Bump Destructurama.Attributed and Serilog in /src
  Bump Microsoft.Extensions.DependencyInjection in /src
  ...
@gittools-bot
Copy link
Contributor

🎉 This issue has been resolved in version 0.19.0 🎉

The release is available on:

Your GitReleaseManager bot 📦🚀

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

Successfully merging a pull request may close this issue.

3 participants