-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: data-time range parameters do not seem to be working correctly #497
Comments
👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with |
That would be a bug with GitHub itself. We don't parse values given as parameters |
Thanks for getting back to me so fast! Do you know where I can open a bug report for the GitHub API? |
IIRC in the past we've pointed people to Community discussions for these types of issues, although you can also file a bug report. |
What happened?
I'm using
@octokit/core
to list workflow runs based on the REST API docs. I'm attempting to use thecreated
parameter with a date-time formatted as2024-07-24T17:00:00Z
, but I don't get any results back. When I only use the date2024-07-24
, I get the correct results back, so I'm not sure if there is a bug in this library (when encoding the parameter), the actual github api, or if the docs need to be updated to specify that only the date portion of the date-time range is available.Versions
Octokit: v6.1.2
Node.js: v20.15.0
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: