-
-
Notifications
You must be signed in to change notification settings - Fork 398
[JENKINS-76026] Do not show merges in changelog #1327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
MarkEWaite
merged 1 commit into
jenkinsci:master
from
MarkEWaite:exclude-merge-commits-from-changelog
Aug 23, 2025
Merged
[JENKINS-76026] Do not show merges in changelog #1327
MarkEWaite
merged 1 commit into
jenkinsci:master
from
MarkEWaite:exclude-merge-commits-from-changelog
Aug 23, 2025
Conversation
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
Git client 6.3.1 adapted the git client plugin to support command line git 2.51.0 where the "whatchanged" command has been deprecated. However, the change introduced an inconsistency between the CLI git implementation and the JGit implementation. Prior to git client plugin 6.3.1, the changelog skipped merge commits in all cases. With git client 6.3.1, the CLI git changelog includes merge commits. With git client 6.3.1, the JGit changelog does not include merge commits. Testing done: * Confirmed the bug with interactive testing of git client plugin 6.3.1 * Wrote an automated test that shows the inconsistency * Confirmed that the automated test fails with git client 6.3.1 and passes with the fix
6 tasks
basil
pushed a commit
to basil/git-client-plugin
that referenced
this pull request
Sep 3, 2025
Git client 6.3.1 adapted the git client plugin to support command line git 2.51.0 where the "whatchanged" command has been deprecated. However, the change introduced an inconsistency between the CLI git implementation and the JGit implementation. Prior to git client plugin 6.3.1, the changelog skipped merge commits in all cases. With git client 6.3.1, the CLI git changelog includes merge commits. With git client 6.3.1, the JGit changelog does not include merge commits. Testing done: * Confirmed the bug with interactive testing of git client plugin 6.3.1 * Wrote an automated test that shows the inconsistency * Confirmed that the automated test fails with git client 6.3.1 and passes with the fix (cherry picked from commit 358e279)
MarkEWaite
added a commit
that referenced
this pull request
Sep 3, 2025
Git client 6.3.1 adapted the git client plugin to support command line git 2.51.0 where the "whatchanged" command has been deprecated. However, the change introduced an inconsistency between the CLI git implementation and the JGit implementation. Prior to git client plugin 6.3.1, the changelog skipped merge commits in all cases. With git client 6.3.1, the CLI git changelog includes merge commits. With git client 6.3.1, the JGit changelog does not include merge commits. Testing done: * Confirmed the bug with interactive testing of git client plugin 6.3.1 * Wrote an automated test that shows the inconsistency * Confirmed that the automated test fails with git client 6.3.1 and passes with the fix (cherry picked from commit 358e279)
MarkEWaite
added a commit
to MarkEWaite/update-center2
that referenced
this pull request
Sep 4, 2025
https://www.jenkins.io/security/advisory/2025-09-03/#SECURITY-3590 is fixed by backporting the changes from Git Client Plugin 6.3.3 Backport from commit 20090a86c3ebc72e5283c882de73e3a4459137bb Git Client Plugin 6.2.1 also includes fixes to support command line git 2.51.0. Those changes were originally from pull requests: * jenkinsci/git-client-plugin#1326 * jenkinsci/git-client-plugin#1327 Fixed by pull request: * jenkinsci/git-client-plugin#1332 Testing done: I've run interactive tests with Git Client Plugin 6.2.1 incremental build and found no issues.
MarkEWaite
added a commit
to MarkEWaite/git-client-plugin
that referenced
this pull request
Sep 4, 2025
Git client 6.3.1 adapted the git client plugin to support command line git 2.51.0 where the "whatchanged" command has been deprecated. However, the change introduced an inconsistency between the CLI git implementation and the JGit implementation. Prior to git client plugin 6.3.1, the changelog skipped merge commits in all cases. With git client 6.3.1, the CLI git changelog includes merge commits. With git client 6.3.1, the JGit changelog does not include merge commits. Testing done: * Confirmed the bug with interactive testing of git client plugin 6.3.1 * Wrote an automated test that shows the inconsistency * Confirmed that the automated test fails with git client 6.3.1 and passes with the fix (cherry picked from commit 358e279)
6 tasks
MarkEWaite
added a commit
that referenced
this pull request
Sep 4, 2025
Git client 6.3.1 adapted the git client plugin to support command line git 2.51.0 where the "whatchanged" command has been deprecated. However, the change introduced an inconsistency between the CLI git implementation and the JGit implementation. Prior to git client plugin 6.3.1, the changelog skipped merge commits in all cases. With git client 6.3.1, the CLI git changelog includes merge commits. With git client 6.3.1, the JGit changelog does not include merge commits. Testing done: * Confirmed the bug with interactive testing of git client plugin 6.3.1 * Wrote an automated test that shows the inconsistency * Confirmed that the automated test fails with git client 6.3.1 and passes with the fix (cherry picked from commit 358e279)
MarkEWaite
added a commit
to MarkEWaite/update-center2
that referenced
this pull request
Sep 4, 2025
https://www.jenkins.io/security/advisory/2025-09-03/#SECURITY-3590 is fixed by backporting the changes from Git Client Plugin 6.3.3 Backport from commit 20090a86c3ebc72e5283c882de73e3a4459137bb Git Client Plugin 6.1.4 also includes fixes to support command line git 2.51.0. Those changes were originally from pull requests: * jenkinsci/git-client-plugin#1326 * jenkinsci/git-client-plugin#1327 Fixed by pull request: * jenkinsci/git-client-plugin#1333 Testing done: I've run interactive tests with a Git Client Plugin 6.1.4 development build and found no issues. Details are described in pull request: * jenkinsci/git-client-plugin#1333
Kevin-CB
pushed a commit
to jenkins-infra/update-center2
that referenced
this pull request
Sep 5, 2025
…#887) * Mark SECURITY-3590 as also fixed in Git Client Plugin 6.2.1 https://www.jenkins.io/security/advisory/2025-09-03/#SECURITY-3590 is fixed by backporting the changes from Git Client Plugin 6.3.3 Backport from commit 20090a86c3ebc72e5283c882de73e3a4459137bb Git Client Plugin 6.2.1 also includes fixes to support command line git 2.51.0. Those changes were originally from pull requests: * jenkinsci/git-client-plugin#1326 * jenkinsci/git-client-plugin#1327 Fixed by pull request: * jenkinsci/git-client-plugin#1332 Testing done: I've run interactive tests with Git Client Plugin 6.2.1 incremental build and found no issues. * Mark SECURITY-3590 as also fixed in Git Client Plugin 6.1.4 https://www.jenkins.io/security/advisory/2025-09-03/#SECURITY-3590 is fixed by backporting the changes from Git Client Plugin 6.3.3 Backport from commit 20090a86c3ebc72e5283c882de73e3a4459137bb Git Client Plugin 6.1.4 also includes fixes to support command line git 2.51.0. Those changes were originally from pull requests: * jenkinsci/git-client-plugin#1326 * jenkinsci/git-client-plugin#1327 Fixed by pull request: * jenkinsci/git-client-plugin#1333 Testing done: I've run interactive tests with a Git Client Plugin 6.1.4 development build and found no issues. Details are described in pull request: * jenkinsci/git-client-plugin#1333
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.
[JENKINS-76026] Do not show merges in changelog
Git client 6.3.1 adapted the git client plugin to support command line git 2.51.0 where the "whatchanged" command has been deprecated. However, the change introduced an inconsistency between the CLI git implementation and the JGit implementation.
Prior to git client plugin 6.3.1, the changelog skipped merge commits in all cases.
With git client 6.3.1, the CLI git changelog includes merge commits. With git client 6.3.1, the JGit changelog does not include merge commits.
Testing done
Submitter checklist