Skip to content

Actions: newren/git

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
206 workflow runs
206 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

merge: reduce prevalence of nested conflicts with diff3 Coverity #68: Commit 35331a2 pushed by newren
January 21, 2025 16:36 3s favor-base
favor-base
January 21, 2025 16:36 3s
merge: reduce prevalence of nested conflicts with diff3 git-l10n #421: Commit 35331a2 pushed by newren
January 21, 2025 16:36 2s favor-base
favor-base
January 21, 2025 16:36 2s
merge: reduce prevalence of nested conflicts with diff3 CI #1213: Commit 35331a2 pushed by newren
January 21, 2025 16:36 39m 6s favor-base
favor-base
January 21, 2025 16:36 39m 6s
merge: reduce prevalence of nested conflicts with diff3 Coverity #67: Commit e82cbb1 pushed by newren
January 21, 2025 15:46 2s favor-base
favor-base
January 21, 2025 15:46 2s
merge: reduce prevalence of nested conflicts with diff3 CI #1212: Commit e82cbb1 pushed by newren
January 21, 2025 15:46 33m 0s favor-base
favor-base
January 21, 2025 15:46 33m 0s
merge: reduce prevalence of nested conflicts with diff3 git-l10n #420: Commit e82cbb1 pushed by newren
January 21, 2025 15:46 1s favor-base
favor-base
January 21, 2025 15:46 1s
object-name: be more strict in parsing describe-like output Coverity #66: Commit 19f84df pushed by newren
January 7, 2025 00:16 2s object-name-fix
object-name-fix
January 7, 2025 00:16 2s
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
object-name-fix
January 7, 2025 00:16 1s
object-name: be more strict in parsing describe-like output CI #1211: Commit 19f84df pushed by newren
January 7, 2025 00:16 45m 31s object-name-fix
object-name-fix
January 7, 2025 00:16 45m 31s
object-name: be more strict in parsing describe-like output CI #1210: Commit e873a40 pushed by newren
January 7, 2025 00:07 17m 10s object-name-fix
object-name-fix
January 7, 2025 00:07 17m 10s
object-name: be more strict in parsing describe-like output Coverity #65: Commit e873a40 pushed by newren
January 7, 2025 00:07 2s object-name-fix
object-name-fix
January 7, 2025 00:07 2s
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
object-name-fix
January 7, 2025 00:07 2s
object-name: be more strict in parsing describe-like output Coverity #64: Commit 31f1c37 pushed by newren
January 3, 2025 23:29 2s object-name-fix
object-name-fix
January 3, 2025 23:29 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
object-name-fix
January 3, 2025 23:29 1s
object-name: be more strict in parsing describe-like output CI #1209: Commit 31f1c37 pushed by newren
January 3, 2025 23:29 40m 4s object-name-fix
object-name-fix
January 3, 2025 23:29 40m 4s
object-name: be more strict in parsing describe-like output Coverity #63: Commit 68bc921 pushed by newren
January 3, 2025 23:20 2s object-name-fix
object-name-fix
January 3, 2025 23:20 2s
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
object-name-fix
January 3, 2025 23:20 1s
object-name: be more strict in parsing describe-like output CI #1208: Commit 68bc921 pushed by newren
January 3, 2025 23:20 18m 35s object-name-fix
object-name-fix
January 3, 2025 23:20 18m 35s
Can I get rid of the FUNNYNAME requirement? Coverity #62: Commit 030d909 pushed by newren
January 3, 2025 19:05 3s object-name-fix
object-name-fix
January 3, 2025 19:05 3s
Can I get rid of the FUNNYNAME requirement? CI #1207: Commit 030d909 pushed by newren
January 3, 2025 19:05 35m 45s object-name-fix
object-name-fix
January 3, 2025 19:05 35m 45s
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
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
object-name-fix
January 3, 2025 18:13 1s
Can I get rid of the FUNNYNAME requirement? Coverity #61: Commit 4759f9c pushed by newren
January 3, 2025 18:13 2s object-name-fix
object-name-fix
January 3, 2025 18:13 2s
Can I get rid of the FUNNYNAME requirement? CI #1206: Commit 4759f9c pushed by newren
January 3, 2025 18:13 39m 45s object-name-fix
object-name-fix
January 3, 2025 18:13 39m 45s
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
object-name-fix
January 3, 2025 17:52 1s