Skip to content

Actions: WordPress/openverse

Actions

Issue automations

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
issue_automations.yml
2,046 workflow run results
2,046 workflow run results

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

Simplify just ps script using compose v2's docker compose ps JSON output Issue automations #1921: Issue #4045 labeled by sarayourfriend
April 8, 2024 00:44 24s
April 8, 2024 00:44 24s
Add ability to manually send analytics POST request from the server Issue automations #1920: Issue #3776 unlabeled by obulat
April 6, 2024 04:41 20s
April 6, 2024 04:41 20s
Remove duplicated tags Issue automations #1919: Issue #1566 labeled by krysal
April 5, 2024 17:31 25s
April 5, 2024 17:31 25s
Update raw_tags to avoid duplicates in the catalog Issue automations #1918: Issue #3926 closed by krysal
April 5, 2024 01:53 23s
April 5, 2024 01:53 23s
Update references to audio works to use "audio track(s)" Issue automations #1917: Issue #3972 assigned by dhruvkb
April 4, 2024 20:34 20s
April 4, 2024 20:34 20s
Implementation Plan: Determine and design how machine-generated tags will be displayed/conveyed in the API Issue automations #1916: Issue #4038 assigned by AetherUnbound
April 4, 2024 19:57 2m 58s
April 4, 2024 19:57 2m 58s
Implementation Plan: Augment the catalog database with suitable Rekognition tags Issue automations #1915: Issue #4040 opened by AetherUnbound
April 4, 2024 19:56 26s
April 4, 2024 19:56 26s
Implementation Plan: Augment the catalog database with suitable Rekognition tags Issue automations #1911: Issue #4040 labeled by AetherUnbound
April 4, 2024 19:56 22s
April 4, 2024 19:56 22s
Implementation Plan: Augment the catalog database with suitable Rekognition tags Issue automations #1912: Issue #4040 labeled by AetherUnbound
April 4, 2024 19:56 22s
April 4, 2024 19:56 22s
Implementation Plan: Augment the catalog database with suitable Rekognition tags Issue automations #1913: Issue #4040 labeled by AetherUnbound
April 4, 2024 19:56 24s
April 4, 2024 19:56 24s
Implementation Plan: Augment the catalog database with suitable Rekognition tags Issue automations #1914: Issue #4040 labeled by AetherUnbound
April 4, 2024 19:56 25s
April 4, 2024 19:56 25s
Implementation Plan: Augment the catalog database with suitable Rekognition tags Issue automations #1910: Issue #4040 labeled by AetherUnbound
April 4, 2024 19:56 48s
April 4, 2024 19:56 48s
Implementation Plan: Determine and design how machine-generated tags will be displayed/conveyed in the Frontend Issue automations #1908: Issue #4039 labeled by AetherUnbound
April 4, 2024 19:50 23s
April 4, 2024 19:50 23s
Implementation Plan: Determine and design how machine-generated tags will be displayed/conveyed in the Frontend Issue automations #1909: Issue #4039 opened by AetherUnbound
April 4, 2024 19:50 27s
April 4, 2024 19:50 27s
Implementation Plan: Determine and design how machine-generated tags will be displayed/conveyed in the Frontend Issue automations #1906: Issue #4039 labeled by AetherUnbound
April 4, 2024 19:50 22s
April 4, 2024 19:50 22s
Implementation Plan: Determine and design how machine-generated tags will be displayed/conveyed in the Frontend Issue automations #1904: Issue #4039 labeled by AetherUnbound
April 4, 2024 19:50 22s
April 4, 2024 19:50 22s
Implementation Plan: Determine and design how machine-generated tags will be displayed/conveyed in the Frontend Issue automations #1905: Issue #4039 labeled by AetherUnbound
April 4, 2024 19:50 26s
April 4, 2024 19:50 26s
Implementation Plan: Determine and design how machine-generated tags will be displayed/conveyed in the Frontend Issue automations #1907: Issue #4039 labeled by AetherUnbound
April 4, 2024 19:50 21s
April 4, 2024 19:50 21s
Implementation Plan: Determine and design how machine-generated tags will be displayed/conveyed in the API Issue automations #1903: Issue #4038 labeled by AetherUnbound
April 4, 2024 19:44 27s
April 4, 2024 19:44 27s
Implementation Plan: Determine and design how machine-generated tags will be displayed/conveyed in the API Issue automations #1902: Issue #4038 opened by AetherUnbound
April 4, 2024 19:44 22s
April 4, 2024 19:44 22s
Implementation Plan: Determine and design how machine-generated tags will be displayed/conveyed in the API Issue automations #1900: Issue #4038 labeled by AetherUnbound
April 4, 2024 19:44 23s
April 4, 2024 19:44 23s
Implementation Plan: Determine and design how machine-generated tags will be displayed/conveyed in the API Issue automations #1899: Issue #4038 labeled by AetherUnbound
April 4, 2024 19:44 24s
April 4, 2024 19:44 24s
Implementation Plan: Determine and design how machine-generated tags will be displayed/conveyed in the API Issue automations #1901: Issue #4038 labeled by AetherUnbound
April 4, 2024 19:44 28s
April 4, 2024 19:44 28s
Implementation Plan: Determine and design how machine-generated tags will be displayed/conveyed in the API Issue automations #1898: Issue #4038 labeled by AetherUnbound
April 4, 2024 19:44 22s
April 4, 2024 19:44 22s
Define shape for API JSONFields and validate data entering the API from the catalog Issue automations #1897: Issue #4036 opened by dhruvkb
April 4, 2024 14:57 24s
April 4, 2024 14:57 24s