Skip to content

Actions: newren/git

Actions

git-l10n

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
69 workflow runs
69 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

merge: reduce prevalence of nested conflicts with diff3
git-l10n #421: Commit 35331a2 pushed by newren
January 21, 2025 16:36 2s favor-base
January 21, 2025 16:36 2s
merge: reduce prevalence of nested conflicts with diff3
git-l10n #420: Commit e82cbb1 pushed by newren
January 21, 2025 15:46 1s favor-base
January 21, 2025 15:46 1s
object-name: be more strict in parsing describe-like output
git-l10n #419: Commit 19f84df pushed by newren
January 7, 2025 00:16 1s object-name-fix
January 7, 2025 00:16 1s
object-name: be more strict in parsing describe-like output
git-l10n #418: Commit e873a40 pushed by newren
January 7, 2025 00:07 2s object-name-fix
January 7, 2025 00:07 2s
object-name: be more strict in parsing describe-like output
git-l10n #417: Commit 31f1c37 pushed by newren
January 3, 2025 23:29 1s object-name-fix
January 3, 2025 23:29 1s
object-name: be more strict in parsing describe-like output
git-l10n #416: Commit 68bc921 pushed by newren
January 3, 2025 23:20 1s object-name-fix
January 3, 2025 23:20 1s
Can I get rid of the FUNNYNAME requirement?
git-l10n #415: Commit 030d909 pushed by newren
January 3, 2025 19:05 2s object-name-fix
January 3, 2025 19:05 2s
Can I get rid of the FUNNYNAME requirement?
git-l10n #414: Commit 4759f9c pushed by newren
January 3, 2025 18:13 1s object-name-fix
January 3, 2025 18:13 1s
Can I get rid of the FUNNYNAME requirement?
git-l10n #413: Commit f6e6e7a pushed by newren
January 3, 2025 17:52 1s object-name-fix
January 3, 2025 17:52 1s
December 30, 2024 19:57 1s
December 30, 2024 19:25 2s
doc: correct misleading descriptions for --shallow-exclude
git-l10n #398: Commit 4c7f2db pushed by newren
November 4, 2024 17:00 1s shallow-exclude
November 4, 2024 17:00 1s