You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or 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
Merged PRs are listed individually.
For commits, it includes a link to the commit history since the last tag
Nice thing is, it determines the last tag automatically based on branch defined
The PRs we merge for rebases and fixes and such would be listed individually with some details and specific links
If there are only package updates by the bot, there would be a link to an accurate changelog with all the commits since the last tag.
However, if the new release includes an upstream version update only, no package updates and the upstream app's version is not listed in the package_versions.txt, this method would list the changelog between the prior tag (as opposed to latest) and the new prpoposed tag. It wouldn't be inaccurate, but it would be misleading. It now checks to see if the current commit is associated with a tag and if so, it prints No Changes under the LS changes section.
EDIT: Switched to jq for generating our release body because sanitization became a nightmare. The above releases were created by copy pasting the api call output into a manually created released.
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.
github-project-automation
bot
moved this from PRs Ready For Team Review
to PRs Approved
in Issue & PR Tracker
Merged PRs are listed individually.
For commits, it includes a link to the commit history since the last tag
Nice thing is, it determines the last tag automatically based on branch defined
However, if the new release includes an upstream version update only, no package updates and the upstream app's version is not listed in the package_versions.txt, this method would list the changelog between the prior tag (as opposed to latest) and the new prpoposed tag. It wouldn't be inaccurate, but it would be misleading.It now checks to see if the current commit is associated with a tag and if so, it printsNo Changesunder the LS changes section.Here are some examples:
Release with PRs: https://github.com/aptalca/test/releases/tag/1.0.1
Release with No PRs, just commits: https://github.com/aptalca/test/releases/tag/test-1.0.1
Release with just commits and no previous tag: https://github.com/aptalca/test/releases/tag/test-1.0.0
EDIT: Switched to jq for generating our release body because sanitization became a nightmare. The above releases were created by copy pasting the api call output into a manually created released.
The following release was created entirely via cli, mimicking the Jenkinsfile commands as closely as possible: https://github.com/aptalca/test/releases/tag/140.0.7339.80-1-ls36