Skip to content

Closed issues reported under the wrong milestone #638

@ferrarimarco

Description

@ferrarimarco

Hi @skywinder @olleolleolle
I don't know if I'm missing something here, but in one of my changelogs some issues are reported under the wrong milestone (the --[no-]filter-by-milestone option makes no difference):

Project: https://github.com/scissor-project/open-scissor

Some examples of wrongly-filed issues:

  • Issue 1: created 2017-10-27, closed 2018-01-22, filed under 2.0.0 milestone, appears under 1.0.1
  • Issue 12: created 2017-11-11, closed 2018-01-26, filed under 2.0.0 milestone, appears under 1.0.1

Some examples of correctly-filed issues for the 2.0.0 (not yet released version):

  • Issue 60: created 2018-03-26, closed 2018-03-27, filed under 2.0.0 milestone, appears under 2.0.0
  • Issue 61: created 2018-04-06, closed 2018-04-06, filed under 2.0.0 milestone, appears under 2.0.0

Tags:

  • 1.0.0: tagged on 2017-12-11
  • 1.0.1: tagged on 2018-03-26

Milestones:

  • 1.0.0: closed on 2017-12-11
  • 1.0.1: closed on 2018-03-26
  • 2.0.0: still open

GitHub Changelog Generator version: 1.14.3

How to reproduce: github_changelog_generator -t your_token --user scissor-project --project open-scissor

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy