Skip to content

Actions: oborel/obo-relations

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 #556: Scheduled
July 12, 2024 02:01 21s master
July 12, 2024 02:01 21s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #555: Scheduled
July 11, 2024 02:03 22s master
July 11, 2024 02:03 22s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #554: Scheduled
July 10, 2024 02:02 20s master
July 10, 2024 02:02 20s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #553: Scheduled
July 9, 2024 02:02 28s master
July 9, 2024 02:02 28s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #552: Scheduled
July 8, 2024 02:03 26s master
July 8, 2024 02:03 26s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #551: Scheduled
July 7, 2024 02:06 19s master
July 7, 2024 02:06 19s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #550: Scheduled
July 6, 2024 01:57 24s master
July 6, 2024 01:57 24s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #549: Scheduled
July 5, 2024 02:00 22s master
July 5, 2024 02:00 22s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #548: Scheduled
July 4, 2024 02:01 23s master
July 4, 2024 02:01 23s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #547: Scheduled
July 3, 2024 02:00 22s master
July 3, 2024 02:00 22s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #546: Scheduled
July 2, 2024 02:01 28s master
July 2, 2024 02:01 28s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #545: Scheduled
July 1, 2024 02:08 24s master
July 1, 2024 02:08 24s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #544: Scheduled
June 30, 2024 02:05 27s master
June 30, 2024 02:05 27s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #543: Scheduled
June 29, 2024 01:58 27s master
June 29, 2024 01:58 27s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #542: Scheduled
June 28, 2024 02:00 29s master
June 28, 2024 02:00 29s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #541: Scheduled
June 27, 2024 01:59 30s master
June 27, 2024 01:59 30s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #540: Scheduled
June 26, 2024 01:59 20s master
June 26, 2024 01:59 20s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #539: Scheduled
June 25, 2024 02:00 20s master
June 25, 2024 02:00 20s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #538: Scheduled
June 24, 2024 02:01 21s master
June 24, 2024 02:01 21s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #537: Scheduled
June 23, 2024 02:03 21s master
June 23, 2024 02:03 21s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #536: Scheduled
June 22, 2024 01:57 26s master
June 22, 2024 01:57 26s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #535: Scheduled
June 21, 2024 01:58 28s master
June 21, 2024 01:58 28s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #534: Scheduled
June 20, 2024 01:58 28s master
June 20, 2024 01:58 28s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #533: Scheduled
June 19, 2024 02:00 23s master
June 19, 2024 02:00 23s