[GitHub Actions API] Date range syntax not working for query parameter
@nickfloyd is already working on this.
Since Nov 6, 2025.
Assessment
This issue has not been assessed yet.
Description
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
- Dominant language
- No language data
- Stars
- 1.6k
- Forks
- 342
- Avg merge
- 3h 33m
- Merged PRs (30d)
- 51
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/rest-api-description
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
github/rest-api-description#7201 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/rest-api-description#7163 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/rest-api-description#7162 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/rest-api-description#7135 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
github/rest-api-description#7111 · 1 comment ·