-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Property 'issues' does not exist on type 'GitHub' #335
Comments
I was having similar issues on this. I found that my type definition file generated as part of the github actions package here: imports Octokit as a default instead of as a decomposed import: import { graphql as GraphQL } from '@octokit/graphql/dist-types/types';
import Octokit from '@octokit/rest';
import * as Context from './context';
export declare const context: Context.Context;
export declare class GitHub extends Octokit { should be:
this breaks compilation for me. When I hand edit the package with this change, my project compiles. This octokit release seems to be related to this issue. I ended up nuking all my typescript and just using raw node instead, since I couldn't compile using the types supplied by the |
@hardboiled Thanks! That may relate to my PR: #332. |
@nwtgck this should be resolved in I'm going to close this out for now, but if you are still encountering issues please let me know and we can revisit this item. Thanks for your contribution! |
Describe the bug
Hi,
I had the following build error.
I use
@actions/github@2.1.0
. This bug may be a bug of octoki/rest.js.To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: