Open timja opened 2 years ago
Thank you for this feedback 🙇
I am keen for your thoughts on how we could improve this:
repo.json was super confusing that I had to copy your sample repos.json before I could load repos with yarn run getRepos
The reason for this is we had people committing in large files of repos and we got feedback that this was 💩. So We changed it to stop that. Was the README.md
not clear enough? I do want to make this experience better.
Are you a GHES (enterprise server) customer? Or a GHEC customer? The reason I ask is this:
Public repositories were filtered out with no option to enable it on
For GHEC (github.com) everything should automatically be enabled? 👀 so you shouldn't need to enable for any public repos? 🤔
What were you looking to do.
Thanks for the feedback @timja 🙇 I would love to make this better and if there was a bug happy to make changes to get it working.
I am keen for your thoughts on how we could improve this:
There is soo much text in the README.
I skipped passed the instructions and went to this step where I could start copying commands: https://github.com/NickLiffen/ghas-enablement#set-up-instructions
I would suggest creating the file if it doesn't exist, changing the code from doing a straight import of it to using file system APIs and handling it for the user. This step seems really unnecessary if you are running yarn run getRepos
as I want you to load repos.
Are you a GHES (enterprise server) customer? Or a GHEC customer? The reason I ask is this:
Cloud
everything should automatically be enabled What were you looking to do
Push protection and secret scanning is not enabled automatically for public repos. There is a setting to enable it for new ones but no setting to do it retroactively. Sales / account team pointed us at your repo, (which worked perfectly after my hacks)
Note: As shown in the error you do not need to explicitly enable advanced security, but you still do need to enable the features
I would suggest creating the file if it doesn't exist, changing the code from doing a straight import of it to using file system APIs and handling it for the user. This step seems really unnecessary if you are running yarn run getRepos as I want you to load repos.
Will add this to the backlog 👍
Push protection and secret scanning is not enabled automatically for public repos.
hmmm 🤔 I know push protection is but secret scanning should be 🤔 anyway, thanks for the feedback 👍 you obviously ran into a bug, thanks for logging it 👍 I am working on another feature here, but after that will get around to fixing both these problems 🙇
Hey @timja 👋
Just wanted to let you know I fixed this problem:
I would suggest creating the file if it doesn't exist, changing the code from doing a straight import of it to using file system APIs and handling it for the user. This step seems really unnecessary if you are running yarn run getRepos as I want you to load repos. repo.json was super confusing that I had to copy your sample repos.json before I could load repos with yarn run getRepos
I am now going to take a look at this:
Public repositories were filtered out with no option to enable it on Advanced security was force enabled when secretscanning or pushprotection was enabled but public repositories always have AS enabled this caused the script to error out.
Will try and have something done by EOW. I will leave this issue open until both are fixed 👍
I hit a few issues when trying to run this repo.
yarn run getRepos
secretscanning
orpushprotection
was enabled but public repositories always have AS enabled this caused the script to error out.Error:
My diff to make this work:
Anyway thanks for the repo saved me time and it's all working with my hacks