Setting mediaType doesn't work
See original GitHub issueWhat version of octokit is used in this action? I’m trying to get the contents of a file in a repository with:
github.rest.repos.getContent({
owner,
repo,
path,
mediaType: {
format: "raw+json"
}
});
but it doesn’t work. I always get the default response as if mediaType isn’t set. Maybe this is not yet supported in the octokit client used in this action?
I looked at the debug information of the request and the headers don’t include an Accept
header. I expect the Accept
header to be set to application/vnd.github.v3.raw+json
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
How to Fix Missing Paper / Media Type Selection on Apple OSX
SYMPTOM - Paper sizes missing or custom paper sizes not working. FIX - Remove the Airprint driver and replace with the correct one....
Read more >Setting a browser's media type - css - Stack Overflow
The simplest way would be to detect the user's screen resolution using Javascript: screen.width and screen.height . If it's too small, ...
Read more >media - CSS: Cascading Style Sheets - MDN Web Docs
The @media CSS at-rule can be used to apply part of a style sheet based on the result of one or more media...
Read more >Making Changes to Printer Settings - Epson
The Media Type setting determines what other settings are available, so you should always make this setting first. In the Print dialog box,...
Read more >Handle content types - Azure Logic Apps - Microsoft Learn
Learn how to handle various content types in workflows during design ... If you're working with JSON data that doesn't specify a header, ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I ran into the same issue and was able to work around it like this:
Of course this is suboptimal, but at least it behaves the same as when run directly via node locally, or from within custom JS actions.
bug level is on march 3 not updating