Proposed changelog for alpha.2 #1334
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@jim-parry what about: Entity #1213 and also Model #1325 (which is linked with already merged #1189 ) |
|
@nowackipawel The first two you mention have not been merged yet, and #1189 was merged Aug 30, i.e. part of alpha.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@lonnieezell What do you think? It is complete, in terms of which components were changed, but it doesn't say much about what changes were made. I think it we want that, then we need to update the changelog with each merge.
It is based on the PRs merged since alpha.1 ... anything merged directly, and not through a PR, is not included.
PR titles are not useful for automating this, and commit messages are even less useful.