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

Unable to create pull requests #5779

Open
intel352 opened this issue Dec 8, 2024 · 8 comments
Open

Unable to create pull requests #5779

intel352 opened this issue Dec 8, 2024 · 8 comments
Labels
bug Something isn't working UI Any broken visuals like layouts, colors etc.

Comments

@intel352
Copy link

intel352 commented Dec 8, 2024

Version

0.14.3

Operating System

macOS

Distribution Method

dmg (Apple Silicon)

Describe the issue

Launching has this error:

791c3c29d71a47699444192fc95758f6: Not Found - https://docs.github.com/rest/pulls/pulls#list-pull-requests w@tauri://localhost/_app/immutable/chunks/public.D_6bGMXX.js:6:6011 @tauri://localhost/_app/immutable/chunks/public.D_6bGMXX.js:6:8483

Attempting to create a pull request has this error:

Not Found - https://docs.github.com/rest/pulls/pulls#create-a-pull-request

Quite strange. I'm doing this on a new macbook. The last macbook I had was of course running an older release of GitButler, but I'd been able to create and manage PRs from the app.
Something about either the configuration with the new macbook, or else the version of Gitbutler that is active, is leading me into errors that I've not seen before.

I recreated the Github integration authentication. I enabled git signing via ssh, I have git configured to auth via ssh correctly and GitButler tests correctly. I'm not sure what else I need to check.

How to reproduce

No response

Expected behavior

No response

Relevant log output

No response

@intel352 intel352 added the bug Something isn't working label Dec 8, 2024
@Byron
Copy link
Collaborator

Byron commented Dec 9, 2024

Thanks a lot for reporting!

It's interesting that it gets a 404 - Not Found - and the URL looks strange as well. Also, for me it just worked without issues.

CC @estib-vega - maybe this seems familiar.

@estib-vega
Copy link
Contributor

Thanks for tagging me @Byron :)

Hey there @intel352.
Thanks for reporting and sorry for the inconvenience!

I'm also having issues reproducing this.
Is there any thing interesting in the frontend logs?
You should be able to peek into the logs and network calls by opening the browser dev tools option + command + i.

@intel352
Copy link
Author

I'll check on the logs later today, thanks!

@intel352
Copy link
Author

Hmm, it's attempting to hit https://api.github.com/repos/%2FCrisisTextLine/terraform-root-modules/pulls.
Not sure where the %2F came from, seeing if I can find it

@intel352
Copy link
Author

Okay, so the .github/gitbutler/ folder has an unexpected value:

jlangevin@DCF4NW992W gitbutler % ag Crisis
virtual_branches.toml
4:remoteUrl = "[email protected]:/CrisisTextLine/terraform-root-modules.git"

This has to be where the %2F is coming from. Not sure how it originated.

Feel free to close if you don't see a need to check for weird inputs like this :)

@Byron
Copy link
Collaborator

Byron commented Dec 11, 2024

Indeed, the URL has a leading / and that is encoded with %2F as part of the organisation/user name.
I assume after removing it, it worked.

Can you check the output of git remote -v? My guess is that it already contains the slash and somehow Git can deal with it. Maybe it's no issue for SSH-style URLs and it's something we have to specifically handle when processing the URL.

Thanks again.

@intel352
Copy link
Author

intel352 commented Dec 11, 2024 via email

@Byron Byron added the UI Any broken visuals like layouts, colors etc. label Dec 11, 2024
@Byron
Copy link
Collaborator

Byron commented Dec 11, 2024

Maybe the problem is due to not 100% correct handling of URLs in the frontend? Maybe @estib-vega can take a look - ideally that's perfectly testable. The expectation would be this works as some tools seem to be able to produce such partially illformed (but working) URLs.

Alternatively to just making it work, we could of course also show an error that clearly states what the problem is, and how to solve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working UI Any broken visuals like layouts, colors etc.
Projects
None yet
Development

No branches or pull requests

3 participants