-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Please add backstroke-bot with read permission to the repo #1545
Comments
backstroke-bot
with read permission to the repo
I'm not sure if that issue applies to us, we're not a private repository |
I wonder why I am not able to get it working then... ? |
I do not know of any, sorry. I'm sure they exist somewhere! What sort of error are you getting? |
Uhh, error: {"message":"Validation Failed","errors":[{"message":"The listed users and repositories cannot be searched either because the resources do not exist or you do not have permission to view them.","resource":"Search","field":"q","code":"invalid"}],"documentation_url":"https://developer.github.com/v3/search/"} that is if I try the classic mode, which is not well supported anymore... |
I believe you already found it, but I would try using backstroke classic as described here: #682 (comment). |
Are you trying to add backstroke to our repository instead of yours? The error seems to be hinting towards that. Make sure you're using https://github.com/thtliife/create-react-app-storybook-scripts-fork |
After reading the docs, I think those roles should be switched. From should be your repo, To should be create-react-app. |
would that not try to sync pushes from my repo to cra's? |
I'm not sure really, their docs are so confusing. The way you have it pictured is the logical way, but who knows. Once we figure this out we can go ahead and document it for posterity. I'd appreciate if you could do some more research, @thtliife. |
oh no problems @Timer |
In the meantime, I have opened backstrokeapp/server#52 to try to get some clarity... |
I wonder though, if its something to do with the monorepo setup, and maybe backstroke's handling of such a repo? |
@thtliife @Timer I'm the creator of Backstroke. I left a comment on the issue on the Backstroke repo: backstrokeapp/server#52 (comment) I'm going to take a look at Backstroke's docs tonight and see what I can do to make them more clear. Any feedback / suggestions would be very helpful. |
@1egoman @Timer {
"status": "ok",
"output": {
"status": "ok",
"pullRequest": {
"msg": "There's already a pull request for this repo, no need to create another."
},
"isEnabled": true,
"many": false,
"forkCount": 1
}
} |
@Timer will do :) |
As per: backstrokeapp/server#27
When forking cra in order to maintain a custom --scripts-version, using backstroke to keep the fork updated against this repo is very convenient.
This is not possible if
backstroke-bot
does not have read access...The text was updated successfully, but these errors were encountered: