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

NTR: 'is contact information for' CI #652: Pull request #778 synchronize by jmwhorton
January 8, 2024 21:06 1m 30s jmwhorton:ntr/contact-info
jmwhorton:ntr/contact-info
January 8, 2024 21:06 1m 30s
Change label of RO:0002297 to reflect anatomical range. CI #651: Pull request #779 opened by balhoff
January 8, 2024 16:44 1m 30s issue-636
issue-636
January 8, 2024 16:44 1m 30s
Add classification to develops from CI #650: Pull request #724 synchronize by cmungall
January 8, 2024 16:29 1m 31s anitacaron/issue669
anitacaron/issue669
January 8, 2024 16:29 1m 31s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #370: Scheduled
January 8, 2024 01:56 25s master
master
January 8, 2024 01:56 25s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #369: Scheduled
January 7, 2024 02:00 27s master
master
January 7, 2024 02:00 27s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #368: Scheduled
January 6, 2024 01:53 28s master
master
January 6, 2024 01:53 28s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #367: Scheduled
January 5, 2024 01:55 21s master
master
January 5, 2024 01:55 21s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #366: Scheduled
January 4, 2024 01:54 24s master
master
January 4, 2024 01:54 24s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #365: Scheduled
January 3, 2024 01:54 25s master
master
January 3, 2024 01:54 25s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #364: Scheduled
January 2, 2024 01:56 22s master
master
January 2, 2024 01:56 22s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #363: Scheduled
January 1, 2024 02:01 21s master
master
January 1, 2024 02:01 21s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #362: Scheduled
December 31, 2023 01:57 21s master
master
December 31, 2023 01:57 21s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #361: Scheduled
December 30, 2023 01:50 20s master
master
December 30, 2023 01:50 20s
NTR: 'is contact information for' CI #649: Pull request #778 opened by jmwhorton
December 29, 2023 21:25 1m 29s jmwhorton:ntr/contact-info
jmwhorton:ntr/contact-info
December 29, 2023 21:25 1m 29s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #360: Scheduled
December 29, 2023 01:42 24s master
master
December 29, 2023 01:42 24s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #359: Scheduled
December 28, 2023 01:52 23s master
master
December 28, 2023 01:52 23s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #358: Scheduled
December 27, 2023 01:52 27s master
master
December 27, 2023 01:52 27s
NTR: 'has maximum capacity' CI #648: Pull request #777 opened by jmwhorton
December 26, 2023 20:34 1m 30s jmwhorton:ntr/max-capacity
jmwhorton:ntr/max-capacity
December 26, 2023 20:34 1m 30s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #357: Scheduled
December 26, 2023 01:52 23s master
master
December 26, 2023 01:52 23s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #356: Scheduled
December 25, 2023 01:55 29s master
master
December 25, 2023 01:55 29s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #355: Scheduled
December 24, 2023 01:56 22s master
master
December 24, 2023 01:56 22s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #354: Scheduled
December 23, 2023 01:50 22s master
master
December 23, 2023 01:50 22s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #353: Scheduled
December 22, 2023 01:53 22s master
master
December 22, 2023 01:53 22s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #352: Scheduled
December 21, 2023 01:54 23s master
master
December 21, 2023 01:54 23s
Mark and close stale issues and identify stale pull requests Mark and close stale issues and identify stale pull requests #351: Scheduled
December 20, 2023 01:34 25s master
master
December 20, 2023 01:34 25s
ProTip! You can narrow down the results and go further in time using created:<2023-12-20 or the other filters available.