ruby.git/tool/test/test_sync_default_gems.rb, branch v4.0.4 The Ruby Programming Language test_sync_default_gems.rb: Omit if git is v2.43 or older 2025-12-17T18:45:57+00:00 Takashi Kokubun takashikkbn@gmail.com 2025-12-17T18:44:28+00:00 f7120860b0a76fd776ef4bf040e42a46c8aeff63 






Omit a test on s390x linux tripping over a git bug
2025-11-20T00:03:23+00:00

Alan Wu
XrXr@users.noreply.github.com

2025-11-20T00:03:23+00:00

167c3dbaa052d7ad34c374fc6c5f2cceab76b3ac

This test has been reliably failing on recent trunk versions.

See: <https://github.com/ruby/ruby/actions/runs/19519712433/job/55880266450#step:14:120>




This test has been reliably failing on recent trunk versions.

See: <https://github.com/ruby/ruby/actions/runs/19519712433/job/55880266450#step:14:120>






Exclude lib/unicode_normalize from lib/un
2025-11-13T12:27:53+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2025-11-13T11:50:45+00:00

4a1b88afb82291bd066472e8ad0000b23ed0d4dc












sync_default_gems.rb: gracefully handle merge commits
2025-11-05T06:01:16+00:00

Kazuki Yamaguchi
k@rhe.jp

2025-10-28T12:55:09+00:00

f979ef1fb34569cfa34f00691591feac58b27842

Find interesting commits by following parents instead of relying on
"git log".

If we encounter a merge commit that may contain a conflict resolution,
fall back to cherry-picking the merge commit as a whole rather than
replaying each individual commit. The sync commit will include a
shortlog for the squashed commits in that case.





Find interesting commits by following parents instead of relying on
"git log".

If we encounter a merge commit that may contain a conflict resolution,
fall back to cherry-picking the merge commit as a whole rather than
replaying each individual commit. The sync commit will include a
shortlog for the squashed commits in that case.







sync_default_gems.rb: use declarative mapping rules
2025-11-05T06:01:16+00:00

Kazuki Yamaguchi
k@rhe.jp

2025-10-30T10:34:22+00:00

b722631b481314023b9fa2f3fd16fa9ab0b4bf9c

No behavior change is intended by this change.





No behavior change is intended by this change.







sync_default_gems.rb: simplify rewriting commit message
2025-11-05T06:01:16+00:00

Kazuki Yamaguchi
k@rhe.jp

2025-10-28T12:34:41+00:00

348adb8fb46c815b1ec16f05d1beceef270ef0ec

Use "git commit --amend" instead of "git filter-branch" since we only
need to handle one commit at HEAD.





Use "git commit --amend" instead of "git filter-branch" since we only
need to handle one commit at HEAD.







Skip `TestSyncWithCommits` on other than particular platforms
2025-09-17T05:34:58+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2025-09-17T02:31:34+00:00

e92543e76c13c257664e23d8f95a156e7cf9aef5

No one uses `sync_default_gems_with` on other platforms; it is used by
the dedicated workflow and a few developers only.





No one uses `sync_default_gems_with` on other platforms; it is used by
the dedicated workflow and a few developers only.







sync_default_gems.rb: Set git configurations for EOL code of logs
2025-09-17T02:23:17+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2025-09-16T23:16:14+00:00

13a57c9c35866f25b0b12fbe4c4df475711b09eb












sync_default_gems.rb: Support `log.showSignature` case
2025-09-07T01:41:32+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2025-09-06T23:27:13+00:00

85bd3fb870aca52c778cf32be424e13a1372fbf1












Test_SyncDefaultGems: Fail when editor run (#9365)
2023-12-26T21:43:23+00:00

Sorah Fukumori
her@sorah.jp

2023-12-26T21:43:23+00:00

fac253677604e5acc6a49b632355616b068d5a15

When something went wrong and git launches editor, and a editor chosen
was terminal-based, a test run unnoticeably hangs.

As we intend editors not to be ran with --no-edit, GIT_EDITOR should be
defaulted to `false` so let Git command fails when it attempts to start a
editor. This allows catching such unintentional behaviour in test suite.

(Note: Prior to Git v2.32.0, git cherry-pick --no-edit doesn't work for
conflict resolution so currently the test hangs when older Git is in use.
https://github.com/git/git/commit/39edfd5cbc4d168db19ec1bc867d78ec7211ec39
i.e. Ubuntu 20.04, Debian Bullseye doesn't satisfy this prerequisite.)




When something went wrong and git launches editor, and a editor chosen
was terminal-based, a test run unnoticeably hangs.

As we intend editors not to be ran with --no-edit, GIT_EDITOR should be
defaulted to `false` so let Git command fails when it attempts to start a
editor. This allows catching such unintentional behaviour in test suite.

(Note: Prior to Git v2.32.0, git cherry-pick --no-edit doesn't work for
conflict resolution so currently the test hangs when older Git is in use.
https://github.com/git/git/commit/39edfd5cbc4d168db19ec1bc867d78ec7211ec39
i.e. Ubuntu 20.04, Debian Bullseye doesn't satisfy this prerequisite.)