Skip to content

Actions: oborel/obo-relations

Mark and close stale issues and identify stale pull requests

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
440 workflow runs
440 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 #774: Scheduled
February 15, 2025 02:14 20s master
February 15, 2025 02:14 20s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #773: Scheduled
February 14, 2025 02:15 19s master
February 14, 2025 02:15 19s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #772: Scheduled
February 13, 2025 02:15 25s master
February 13, 2025 02:15 25s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #771: Scheduled
February 12, 2025 02:14 18s master
February 12, 2025 02:14 18s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #770: Scheduled
February 11, 2025 02:16 24s master
February 11, 2025 02:16 24s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #769: Scheduled
February 10, 2025 02:15 17s master
February 10, 2025 02:15 17s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #768: Scheduled
February 9, 2025 02:17 17s master
February 9, 2025 02:17 17s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #767: Scheduled
February 8, 2025 02:11 24s master
February 8, 2025 02:11 24s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #766: Scheduled
February 7, 2025 02:15 23s master
February 7, 2025 02:15 23s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #765: Scheduled
February 6, 2025 02:14 24s master
February 6, 2025 02:14 24s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #764: Scheduled
February 5, 2025 02:14 19s master
February 5, 2025 02:14 19s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #763: Scheduled
February 4, 2025 02:12 23s master
February 4, 2025 02:12 23s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #762: Scheduled
February 3, 2025 02:13 23s master
February 3, 2025 02:13 23s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #761: Scheduled
February 2, 2025 02:15 20s master
February 2, 2025 02:15 20s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #760: Scheduled
February 1, 2025 02:16 19s master
February 1, 2025 02:16 19s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #759: Scheduled
January 31, 2025 02:12 19s master
January 31, 2025 02:12 19s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #758: Scheduled
January 30, 2025 02:11 18s master
January 30, 2025 02:11 18s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #757: Scheduled
January 29, 2025 02:11 25s master
January 29, 2025 02:11 25s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #756: Scheduled
January 28, 2025 02:12 16s master
January 28, 2025 02:12 16s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #755: Scheduled
January 27, 2025 02:14 24s master
January 27, 2025 02:14 24s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #754: Scheduled
January 26, 2025 02:15 19s master
January 26, 2025 02:15 19s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #753: Scheduled
January 25, 2025 02:08 17s master
January 25, 2025 02:08 17s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #752: Scheduled
January 24, 2025 02:13 19s master
January 24, 2025 02:13 19s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #751: Scheduled
January 23, 2025 02:12 19s master
January 23, 2025 02:12 19s
Mark and close stale issues and identify stale pull requests
Mark and close stale issues and identify stale pull requests #750: Scheduled
January 22, 2025 02:15 22s master
January 22, 2025 02:15 22s