[GitHub Actions API] Date range syntax not working for query parameter
Los mantenedores suelen responder en 1 día
@nickfloyd ya está trabajando en esto.
Desde el 6/11/2025.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Code of Conduct
- I have read and agree to the GitHub Docs project's Code of Conduct
What article on docs.github.com is affected?
What part(s) of the article would you like to see updated?
Under List workflow runs for a repository, for the query parameter created, the date range syntax has been linked i.e. Query for dates:
# syntax
created:<START-DATE>..<END-DATE>
# example
created:2023-02-10..2023-02-12
But, this doesn't work.
The syntax that works is with =:
created=<START-DATE>..<END-DATE>
created=2023-02-10..2023-02-12
Example
Tested with a public repo like this (created:2023-02-12..2023-02-13):
curl \
-H "Accept: application/vnd.github+json" \
-H "X-GitHub-Api-Version: 2022-11-28" \
"https://api.github.com/repos/iamazeem/test/actions/runs?created:2023-02-12..2023-02-13" \
| jq .total_count
# output: 8
Also, tested with other ranges and it always returns the total number of workflows runs i.e. 8 (at the time of writing).
However, it returns the correct number of workflows when tested with = (created=2023-02-12..2023-02-13):
curl \
-H "Accept: application/vnd.github+json" \
-H "X-GitHub-Api-Version: 2022-11-28" \
"https://api.github.com/repos/iamazeem/test/actions/runs?created=2023-02-12..2023-02-13" \
| jq .total_count
# output: 3
The same has been tested and verified with multiple ranges with : and =.
And, = always work.
Seems like the syntax with : works for GitHub directly:
https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories
But, it doesn't work for GHA API.
Maybe, the article needs to be updated or the link needs to be fixed.
Additional information
No response
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 1.6k
- Forks
- 345
- Merge medio
- 7 h 29 min
- PR fusionados (30 d)
- 62
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/rest-api-description
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
github/rest-api-description#7246 ·
Los mantenedores suelen responder en 1 día
-
feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
github/rest-api-description#7220 ·
Los mantenedores suelen responder en 1 día
-
feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
github/rest-api-description#7201 ·
Los mantenedores suelen responder en 1 día
-
feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
github/rest-api-description#7163 ·
Los mantenedores suelen responder en 1 día
-
Runner deprecations: registration_deprecates_at is declared on the response but never returnedAbiertofeature
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
github/rest-api-description#7162 ·
Los mantenedores suelen responder en 1 día