| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Travis Plunk (@TravisEz13) Since this functionality requires an additional parameter ThisReleaseTag I have avoided making changes to Get-ChangeLog. If you would like to to make changes, you could push to this branch on xtqqczze/PowerShell-PowerShell. |
Sorry, something went wrong.
|
Aditya Patwardhan (@adityapatwardhan) Should be port this to 7.0? |
Sorry, something went wrong.
|
PoshChan-Bot (@PoshChan) Please remind me in 4 hours |
Sorry, something went wrong.
|
Travis Plunk (@TravisEz13), this is the reminder you requested 4 hours ago |
Sorry, something went wrong.
Address @ TravisEz13 review
|
PR is ready to merge. |
Sorry, something went wrong.
|
Hello Travis Plunk (@TravisEz13)! Because this pull request has the AutoMerge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass. p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here. |
Sorry, something went wrong.
# Conflicts: # CHANGELOG/6.2.md
|
🎉v7.0.0-rc.3 has been released which incorporates this pull request.:tada: Handy links: |
Sorry, something went wrong.
|
Travis Plunk (@TravisEz13) Any further improvements to the changelog generation script you think could be made? |
Sorry, something went wrong.
|
Personally, I think the build and packaging section, should just list the PR numbers and not the description (perhaps thank any non-microsoft contributor). |
Sorry, something went wrong.
|
Or better yet list it as details, for example 11736 Update changelog generation<details> <summary>11736</summary> Update changelog generation </details> |
Sorry, something went wrong.
# PR Summary * Fix regression from PowerShell#11652 * Fix [MD022](https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md032---lists-should-be-surrounded-by-blank-lines) / [MD032](https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md032---lists-should-be-surrounded-by-blank-lines) rule violations * Modify `Get-ChangeLog` to generate the changelog according to the format from PowerShell#11652. ## PR Context Follow-up to PowerShell#11652 ## PR Checklist - [x] [PR has a meaningful title](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission) - Use the present tense and imperative mood when describing your changes - [x] [Summarized changes](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission) - [x] [Make sure all `.h`, `.cpp`, `.cs`, `.ps1` and `.psm1` files have the correct copyright header](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission) - [x] This PR is ready to merge and is not [Work in Progress](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---work-in-progress). - If the PR is work in progress, please add the prefix `WIP:` or `[ WIP ]` to the beginning of the title (the `WIP` bot will keep its status check at `Pending` while the prefix is present) and remove the prefix when the PR is ready. - **[Breaking changes](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#making-breaking-changes)** - [x] None - **OR** - [ ] [Experimental feature(s) needed](https://github.com/MicrosoftDocs/PowerShell-Docs/blob/staging/reference/6/Microsoft.PowerShell.Core/About/about_Experimental_Features.md) - [ ] Experimental feature name(s): <!-- Experimental feature name(s) here --> - **User-facing changes** - [x] Not Applicable - **OR** - [ ] [Documentation needed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission) - [ ] Issue filed: <!-- Number/link of that issue here --> - **Testing - New and feature** - [x] N/A or can only be tested interactively - **OR** - [ ] [Make sure you've added a new test if existing tests do not effectively test the code changed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#before-submitting) - **Tooling** - [x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted. - **OR** - [ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include: - Impact on [PowerShell Editor Services](https://github.com/PowerShell/PowerShellEditorServices) which is used in the [PowerShell extension](https://github.com/PowerShell/vscode-powershell) for VSCode (which runs in a different PS Host). - Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features. - Impact on [PSScriptAnalyzer](https://github.com/PowerShell/PSScriptAnalyzer) (which provides linting & formatting in the editor extensions). - Impact on [EditorSyntax](https://github.com/PowerShell/EditorSyntax) (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
| Back | FazBrowse Home | New Git URL |
PR Summary
PR Context
Follow-up to #11652
PR Checklist