Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[FEAT]: Ability to specify etag on request #2926

Open
1 task done
EvgenyKhaliper opened this issue Jun 4, 2024 · 0 comments
Open
1 task done

[FEAT]: Ability to specify etag on request #2926

EvgenyKhaliper opened this issue Jun 4, 2024 · 0 comments
Labels
Status: Triage This is being looked at and prioritized Status: Up for grabs Issues that are ready to be worked on by anyone Type: Feature New feature or request

Comments

@EvgenyKhaliper
Copy link

Describe the need

Currently, there is no way (I know of) to specify an etag during an API call to prevent limits hit.
I have multiple instances of an application that has to access Github API when a change has been made.
Without specifying an etag (which the application saves) there is no real way to avoid limits hit.

Is it possible to expose the ability to specify an etag, like you do in Caching layer?

SDK Version

No response

API Version

No response

Relevant log output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@EvgenyKhaliper EvgenyKhaliper added Status: Triage This is being looked at and prioritized Type: Feature New feature or request labels Jun 4, 2024
@nickfloyd nickfloyd added the Status: Up for grabs Issues that are ready to be worked on by anyone label Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Status: Triage This is being looked at and prioritized Status: Up for grabs Issues that are ready to be worked on by anyone Type: Feature New feature or request
Projects
🧰 Octokit Active
Status: 🔥 Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nickfloyd @EvgenyKhaliper