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.

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

deleted #85

Closed
basel-ui opened this issue Aug 3, 2022 · 3 comments
Closed

deleted #85

basel-ui opened this issue Aug 3, 2022 · 3 comments

Comments

@basel-ui
Copy link

basel-ui commented Aug 3, 2022

No description provided.

@NickLiffen
Copy link
Owner

In your .env you have two ENABLE_ON could you remove one of them, as such it's this:

ENABLE_ON=codescanning,secretscanning

(just to test it on these two please 🙇)

And just to triple check, you ran npm run getRepos firstly, and that ran successfully, correct?

Could you update the .env with the above value (ENABLE_ON=codescanning,secretscanning, re-run npm run getRepos and then run npm run start again please 🙇

Can you also make sure the PAT has the right scopes. E.G repo, workflow and read:org 🙇

@NickLiffen
Copy link
Owner

NickLiffen commented Aug 3, 2022

@basel-ui 👋 question, is this an empty repo, Have there ever been any commits to this repository before? 🤔 If the answer is yes, does that repository have a main branch as it's default branch? Just triple checking

@basel-ui basel-ui closed this as completed Aug 3, 2022
@NickLiffen
Copy link
Owner

@basel-ui I see you closed this out, I would love to know if this is working for you/if you need anything else from me?

@basel-ui basel-ui changed the title https 404 Error deleted Aug 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants