Skip to content

Actions: oborel/obo-relations

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
666 workflow runs
666 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #388: Scheduled
January 26, 2024 01:50 29s master
master
January 26, 2024 01:50 29s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #387: Scheduled
January 25, 2024 01:59 23s master
master
January 25, 2024 01:59 23s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #386: Scheduled
January 24, 2024 01:58 26s master
master
January 24, 2024 01:58 26s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #385: Scheduled
January 23, 2024 01:58 23s master
master
January 23, 2024 01:58 23s
WIP: collected during relation CI #663: Pull request #759 synchronize by anitacaron
January 22, 2024 19:52 1m 31s issue-#598-part2
issue-#598-part2
January 22, 2024 19:52 1m 31s
WIP: collected during relation CI #662: Pull request #759 synchronize by anitacaron
January 22, 2024 19:45 1m 32s issue-#598-part2
issue-#598-part2
January 22, 2024 19:45 1m 32s
NTR "has life cycle stage" relation CI #661: Pull request #742 synchronize by anitacaron
January 22, 2024 19:27 1m 35s issue-#598
issue-#598
January 22, 2024 19:27 1m 35s
measures characteristic CI #660: Pull request #717 synchronize by ddooley
January 22, 2024 04:49 1m 32s ddooley:issue#658
ddooley:issue#658
January 22, 2024 04:49 1m 32s
measures characteristic CI #659: Pull request #717 synchronize by ddooley
January 22, 2024 04:24 1m 3s ddooley:issue#658
ddooley:issue#658
January 22, 2024 04:24 1m 3s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #384: Scheduled
January 22, 2024 02:01 23s master
master
January 22, 2024 02:01 23s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #383: Scheduled
January 21, 2024 02:01 22s master
master
January 21, 2024 02:01 22s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #382: Scheduled
January 20, 2024 01:55 24s master
master
January 20, 2024 01:55 24s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #381: Scheduled
January 19, 2024 01:57 20s master
master
January 19, 2024 01:57 20s
NTR: owns; is owned by CI #658: Pull request #705 synchronize by wdduncan
January 18, 2024 18:43 1m 28s issue-674
issue-674
January 18, 2024 18:43 1m 28s
NTR: owns; is owned by CI #657: Pull request #705 synchronize by wdduncan
January 18, 2024 16:56 1m 30s issue-674
issue-674
January 18, 2024 16:56 1m 30s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #380: Scheduled
January 18, 2024 01:56 29s master
master
January 18, 2024 01:56 29s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #379: Scheduled
January 17, 2024 01:57 27s master
master
January 17, 2024 01:57 27s
NTR: owns; is owned by CI #656: Pull request #705 synchronize by wdduncan
January 16, 2024 17:42 1m 36s issue-674
issue-674
January 16, 2024 17:42 1m 36s
NTR: owns; is owned by CI #655: Pull request #705 synchronize by wdduncan
January 16, 2024 17:01 1m 36s issue-674
issue-674
January 16, 2024 17:01 1m 36s
NTR: owns; is owned by CI #654: Pull request #705 synchronize by anitacaron
January 16, 2024 16:43 1m 29s issue-674
issue-674
January 16, 2024 16:43 1m 29s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #378: Scheduled
January 16, 2024 01:57 22s master
master
January 16, 2024 01:57 22s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #377: Scheduled
January 15, 2024 01:59 24s master
master
January 15, 2024 01:59 24s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #376: Scheduled
January 14, 2024 02:00 24s master
master
January 14, 2024 02:00 24s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #375: Scheduled
January 13, 2024 01:55 21s master
master
January 13, 2024 01:55 21s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #374: Scheduled
January 12, 2024 01:57 20s master
master
January 12, 2024 01:57 20s
ProTip! You can narrow down the results and go further in time using created:<2024-01-12 or the other filters available.