Skip to content

Actions: korpling/graphANNIS

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
834 workflow runs
834 workflow runs
Event

Filter by event

Loading
Status

Filter by status

Loading
Branch
Actor

Filter by actor

Loading
Merge pull request #303 from korpling/feature/use-workflow-run-after-… Code Coverage #228: Commit 1f9f5f0 pushed by thomaskrause
July 4, 2024 15:42 3m 43s main
main
July 4, 2024 15:42 3m 43s
Merge pull request #303 from korpling/feature/use-workflow-run-after-… Static code analysis #839: Commit 1f9f5f0 pushed by thomaskrause
July 4, 2024 15:42 2m 23s main
main
July 4, 2024 15:42 2m 23s
Merge pull request #303 from korpling/feature/use-workflow-run-after-… Automated tests #811: Commit 1f9f5f0 pushed by thomaskrause
July 4, 2024 15:42 2m 59s main
main
July 4, 2024 15:42 2m 59s
Release created by GitHub actions won't trigger the "on release" event, so use the "workflow_run" instead. Append C-API artifact to latest release #7: Pull request #303 labeled by thomaskrause
July 4, 2024 15:33 8m 41s feature/use-workflow-run-after-release
feature/use-workflow-run-after-release
July 4, 2024 15:33 8m 41s
Release created by GitHub actions won't trigger the "on release" event, so use the "workflow_run" instead. Automated tests #810: Pull request #303 opened by thomaskrause
July 4, 2024 15:29 3m 41s feature/use-workflow-run-after-release
feature/use-workflow-run-after-release
July 4, 2024 15:29 3m 41s
Release created by GitHub actions won't trigger the "on release" event, so use the "workflow_run" instead. Code Coverage #227: Pull request #303 opened by thomaskrause
July 4, 2024 15:29 3m 53s feature/use-workflow-run-after-release
feature/use-workflow-run-after-release
July 4, 2024 15:29 3m 53s
Release created by GitHub actions won't trigger the "on release" event, so use the "workflow_run" instead. Static code analysis #838: Pull request #303 opened by thomaskrause
July 4, 2024 15:29 2m 23s feature/use-workflow-run-after-release
feature/use-workflow-run-after-release
July 4, 2024 15:29 2m 23s
Release created by GitHub actions won't trigger the "on release" event, so use the "workflow_run" instead. Release #152: Pull request #303 opened by thomaskrause
July 4, 2024 15:29 26s feature/use-workflow-run-after-release
feature/use-workflow-run-after-release
July 4, 2024 15:29 26s
chore: Release Release #151: Commit 14e1979 pushed by thomaskrause
July 4, 2024 15:02 17m 22s v3.3.2
v3.3.2
July 4, 2024 15:02 17m 22s
Merge pull request #302 from korpling/feature/fix-bematac-issue Append C-API artifact to latest release #6: Commit c25c767 pushed by thomaskrause
July 4, 2024 14:40 4s main
main
July 4, 2024 14:40 4s
Merge pull request #302 from korpling/feature/fix-bematac-issue Code Coverage #226: Commit c25c767 pushed by thomaskrause
July 4, 2024 14:40 11m 2s main
main
July 4, 2024 14:40 11m 2s
Merge pull request #302 from korpling/feature/fix-bematac-issue Automated tests #809: Commit c25c767 pushed by thomaskrause
July 4, 2024 14:40 7m 28s main
main
July 4, 2024 14:40 7m 28s
Merge pull request #302 from korpling/feature/fix-bematac-issue Static code analysis #837: Commit c25c767 pushed by thomaskrause
July 4, 2024 14:40 2m 35s main
main
July 4, 2024 14:40 2m 35s
Load components from backup path if it exists Code Coverage #225: Pull request #302 synchronize by thomaskrause
July 4, 2024 14:34 4m 11s feature/fix-bematac-issue
feature/fix-bematac-issue
July 4, 2024 14:34 4m 11s
Load components from backup path if it exists Release #150: Pull request #302 synchronize by thomaskrause
July 4, 2024 14:34 23s feature/fix-bematac-issue
feature/fix-bematac-issue
July 4, 2024 14:34 23s
Load components from backup path if it exists Automated tests #808: Pull request #302 synchronize by thomaskrause
July 4, 2024 14:34 3m 51s feature/fix-bematac-issue
feature/fix-bematac-issue
July 4, 2024 14:34 3m 51s
Load components from backup path if it exists Static code analysis #836: Pull request #302 synchronize by thomaskrause
July 4, 2024 14:34 2m 57s feature/fix-bematac-issue
feature/fix-bematac-issue
July 4, 2024 14:34 2m 57s
Load components from backup path if it exists Static code analysis #835: Pull request #302 synchronize by thomaskrause
July 4, 2024 14:26 2m 28s feature/fix-bematac-issue
feature/fix-bematac-issue
July 4, 2024 14:26 2m 28s
Load components from backup path if it exists Release #149: Pull request #302 synchronize by thomaskrause
July 4, 2024 14:26 20s feature/fix-bematac-issue
feature/fix-bematac-issue
July 4, 2024 14:26 20s
Load components from backup path if it exists Automated tests #807: Pull request #302 synchronize by thomaskrause
July 4, 2024 14:26 7m 30s feature/fix-bematac-issue
feature/fix-bematac-issue
July 4, 2024 14:26 7m 30s
Load components from backup path if it exists Code Coverage #224: Pull request #302 synchronize by thomaskrause
July 4, 2024 14:26 10m 22s feature/fix-bematac-issue
feature/fix-bematac-issue
July 4, 2024 14:26 10m 22s
Load components from backup path if it exists Automated tests #806: Pull request #302 synchronize by thomaskrause
July 4, 2024 14:24 1d 6h 52m 11s feature/fix-bematac-issue
feature/fix-bematac-issue
July 4, 2024 14:24 1d 6h 52m 11s
Load components from backup path if it exists Code Coverage #223: Pull request #302 synchronize by thomaskrause
July 4, 2024 14:24 10m 43s feature/fix-bematac-issue
feature/fix-bematac-issue
July 4, 2024 14:24 10m 43s
Load components from backup path if it exists Release #148: Pull request #302 synchronize by thomaskrause
July 4, 2024 14:24 20s feature/fix-bematac-issue
feature/fix-bematac-issue
July 4, 2024 14:24 20s
Load components from backup path if it exists Static code analysis #834: Pull request #302 synchronize by thomaskrause
July 4, 2024 14:24 2m 27s feature/fix-bematac-issue
feature/fix-bematac-issue
July 4, 2024 14:24 2m 27s