Bitbucket normalizer #168
Merged
Bitbucket normalizer #168
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
|
thanks |
|
Thank you
…On Sun, 17 Nov 2024, 12:36 Lars Hvam, ***@***.***> wrote:
Merged #168 <#168> into
main.
—
Reply to this email directly, view it on GitHub
<#168 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AASW6HMJAUWU66UJ2QOAYQ32BCEWPAVCNFSM6AAAAABR3VUPS6VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGMZDINZYGI3TKOA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
its published in latest version |
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 is something I needed at work.
reduces noise in diffs, from this:
to this (see line 33):
Not a big deal in projects with strong formatting enforcement like abapgit, it is in some projects.
The bitbucket integration is to keep some extra functionality, normalization will work fine without it. Atlassian doesn't seem very reactive on PRs, doubt it will see the main branch.
I plan to add similar support to github pull requests when I find time