release: fetch changes when creating release for better notes #38
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
xTVaser
force-pushed
the
v/release-notes
branch
from
62fd7d9
to
229158d
Compare
xTVaser
force-pushed
the
v/release-notes
branch
from
229158d
to
d8b5d38
Compare
|
Will need to account for the "new contributor" listing which will cause duplicates - |
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.
This should fetch changes from
jak-projectand from this repo itself to create a JSON string to be consumed by the frontend to provide better patch notes.This should probably be tested but it's not too drastic of a change.
Related to #8