8000 Make sure that all the changes since the last release are associated to the milestone · Issue #37 · doctrine/automatic-releases · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Aug 2, 2020. It is now read-only.
This repository was archived by the owner on Aug 2, 2020. It is now read-only.
Make sure that all the changes since the last release are associated to the milestone #37
Closed
@morozov

Description

@morozov

Right now, for a given pull request, the target branch and the associated milestone are totally independent. It allows for a situation when some changes are released as part of the changes in the branch being tagged but are not listed in the release note. It happens every once in a while.

High-level, the logic is the following:

  1. Take all merge commits since the last release.
  2. Associate them with pull requests on GitHub and the corresponding issues (via the Fixes and Closes references).
  3. If there's a discrepancy, report a problem and halt.
  4. Additionally, if some changes need to be excluded from the notes explicitly, there may be a label for that.

Metadata

Metadata

Assignees

Labels

duplicateThis issue or pull request already existsenhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0