Skip to content

Actions: oborel/obo-relations

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
770 workflow runs
770 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 #507: Scheduled
May 24, 2024 01:56 27s master
master
May 24, 2024 01:56 27s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #506: Scheduled
May 23, 2024 01:55 22s master
master
May 23, 2024 01:55 22s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #505: Scheduled
May 22, 2024 01:56 20s master
master
May 22, 2024 01:56 20s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #504: Scheduled
May 21, 2024 01:55 22s master
master
May 21, 2024 01:55 22s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #503: Scheduled
May 20, 2024 01:58 19s master
master
May 20, 2024 01:58 19s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #502: Scheduled
May 19, 2024 01:58 20s master
master
May 19, 2024 01:58 20s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #501: Scheduled
May 18, 2024 01:54 23s master
master
May 18, 2024 01:54 23s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #500: Scheduled
May 17, 2024 01:55 23s master
master
May 17, 2024 01:55 23s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #499: Scheduled
May 16, 2024 01:55 29s master
master
May 16, 2024 01:55 29s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #498: Scheduled
May 15, 2024 01:58 21s master
master
May 15, 2024 01:58 21s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #497: Scheduled
May 14, 2024 01:54 24s master
master
May 14, 2024 01:54 24s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #496: Scheduled
May 13, 2024 01:57 21s master
master
May 13, 2024 01:57 21s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #495: Scheduled
May 12, 2024 01:58 21s master
master
May 12, 2024 01:58 21s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #494: Scheduled
May 11, 2024 01:52 27s master
master
May 11, 2024 01:52 27s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #493: Scheduled
May 10, 2024 01:57 29s master
master
May 10, 2024 01:57 29s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #492: Scheduled
May 9, 2024 01:56 23s master
master
May 9, 2024 01:56 23s
NTR "has life cycle stage" relation CI #764: Pull request #742 synchronize by ddooley
May 8, 2024 05:36 3m 1s issue-#598
issue-#598
May 8, 2024 05:36 3m 1s
WIP: collected during relation CI #763: Pull request #759 synchronize by ddooley
May 8, 2024 05:18 3m 11s issue-#598-part2
issue-#598-part2
May 8, 2024 05:18 3m 11s
WIP: collected during relation CI #762: Pull request #759 synchronize by ddooley
May 8, 2024 05:08 3m 13s issue-#598-part2
issue-#598-part2
May 8, 2024 05:08 3m 13s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #491: Scheduled
May 8, 2024 01:34 22s master
master
May 8, 2024 01:34 22s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #490: Scheduled
May 7, 2024 01:55 22s master
master
May 7, 2024 01:55 22s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #489: Scheduled
May 6, 2024 01:55 28s master
master
May 6, 2024 01:55 28s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #488: Scheduled
May 5, 2024 01:56 27s master
master
May 5, 2024 01:56 27s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #487: Scheduled
May 4, 2024 01:51 20s master
master
May 4, 2024 01:51 20s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #486: Scheduled
May 3, 2024 01:55 23s master
master
May 3, 2024 01:55 23s