forgejo-contrib-forgejo-cli-issues-221.md
Watch20
Star402
Fork
You've already forked forgejo-cli
CodeIssues 44Pull requests 8Releases 11Packages 2WikiActivity
fj pr create should push the branch to remote #221Open
opened 2025-09-21 21:59:13 +02:00 by untitaker · 2 comments
untitaker commented 2025-09-21 21:59:13 +02:00
Copy link
Feel free to reject these feature requests, this is just another one where github cli works one way but fj cli works another way.
When I run gh pr create, github CLI asks which remote to push it to, and opens the PR against the origin remote.
When I do git checkout -b test2 and fj pr create, I get this error instead:
$ fj pr create testpr
Error: config value 'branch.test2.remote' was not found; class=Config (7); code=NotFound (-3)
Location:
src/prs.rs:962:31
which is fixed with git push --set-upstream origin test2
Feel free to reject these feature requests, this is just another one where github cli works one way but fj cli works another way. When I run gh pr create, github CLI asks which remote to push it to, and opens the PR against the origin remote. When I do git checkout -b test2 and fj pr create, I get this error instead: $ fj pr create testpr Error: config value 'branch.test2.remote' was not found; class=Config (7); code=NotFound (-3) Location: src/prs.rs:962:31 which is fixed with git push --set-upstream origin test2
untitaker changed title from ** fj pr create should push the branch to originfj pr create should push the branch to remote 2025-09-21 21:59:19 +02:00
Cyborus commented 2025-09-21 23:06:31 +02:00
Member
Copy link
I do agree there's improvement to be made in working with forks. I'd prefer not to hard-code the expectation of there being a remote named origin (I tend to name my remotes by what instance they are), but I have thought about adding a way to set a default remote. That could be set during fj repo clone, but it could be clunky in the case of git clone.
When I do git checkout -b test2 and fj pr create, I get this error instead:
I should change this error to tell you to git push --set-upstream .... I might add a --push option to pr create, too, although that might complicate the default remote option.
I do agree there's improvement to be made in working with forks. I'd prefer not to hard-code the expectation of there being a remote named origin (I tend to name my remotes by what instance they are), but I have thought about adding a way to set a default remote. That could be set during fj repo clone, but it could be clunky in the case of git clone. > When I do git checkout -b test2 and fj pr create, I get this error instead: I should change this error to tell you to git push --set-upstream .... I might add a --push option to pr create, too, although that might complicate the default remote option.
untitaker commented 2025-09-21 23:08:24 +02:00
Author
Copy link
I don't know if origin is hard coded in GitHub cli, I just assume that's how it works. it's quite interactive which I don't like that much either.
I don't know if origin is hard coded in GitHub cli, I just assume that's how it works. it's quite interactive which I don't like that much either.
👍 1
Sign in to join this conversation.
No Branch/Tag specified
main
renovate/lock-file-maintenance
renovate/serde-saphyr-0.x
docs/contributing
no-port-in-refspec
login/v16.next.forgejo.org
crates-io-publish
0.5.x
compile-time-fluent
0.4.x
localization-alias-demo
api_url_field
v0.5.0
v0.4.1
v0.4.0
v0.3.0
v0.2.0
v0.1.1
v0.1.0
v0.0.4
v0.0.3
v0.0.2
v0.0.1
Labels
Clear labels[ Kind/Breaking Breaking change that won't be backward compatible
](#)[ Kind/Bug Something is not working
](#)[ Kind/Design Discussion about UI/UX design
](#)[ Kind/Documentation Documentation changes
](#)[ Kind/Enhancement Improve existing functionality
](#)[ Kind/Feature New functionality
](#)[ Kind/Security This is security issue
](#)[ Kind/Testing Issue or pull request related to testing
](#)[ Kind/Upstream This is an issue with upstream software (Forgejo) that is probably not our fault
](#)
[ Priority
Critical The priority is critical
](#)[ Priority
High The priority is high
](#)[ Priority
Low The priority is low
](#)[ Priority
Medium The priority is medium
](#)
[ Reviewed
Confirmed Issue has been confirmed
](#)[ Reviewed
Duplicate This issue or pull request already exists
](#)[ Reviewed
Invalid Invalid issue
](#)[ Reviewed
Won't Fix This issue won't be fixed
](#)
[ Status
Abandoned Somebody has started to work on this but abandoned work
](#)[ Status
Blocked Something is blocking this issue or pull request
](#)[ Status
Need More Info Feedback is required to reproduce issue or to continue work
](#)
[ Suspicious
](#)
No labels Kind/Breaking Kind/Bug Kind/Design Kind/Documentation Kind/Enhancement Kind/Feature Kind/Security Kind/Testing Kind/Upstream [ Priority
Critical ](/forgejo-contrib/forgejo-cli/issues?labels=173012) [ Priority
High ](/forgejo-contrib/forgejo-cli/issues?labels=173013) [ Priority
Low ](/forgejo-contrib/forgejo-cli/issues?labels=173015) [ Priority
Medium ](/forgejo-contrib/forgejo-cli/issues?labels=173014) [ Reviewed
Confirmed ](/forgejo-contrib/forgejo-cli/issues?labels=173007) [ Reviewed
Duplicate ](/forgejo-contrib/forgejo-cli/issues?labels=173005) [ Reviewed
Invalid ](/forgejo-contrib/forgejo-cli/issues?labels=173006) [ Reviewed
Won't Fix ](/forgejo-contrib/forgejo-cli/issues?labels=173008) [ Status
Abandoned ](/forgejo-contrib/forgejo-cli/issues?labels=173011) [ Status
Blocked ](/forgejo-contrib/forgejo-cli/issues?labels=173010) [ Status
Need More Info ](/forgejo-contrib/forgejo-cli/issues?labels=173009) Suspicious
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
Notifications Subscribe
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".
No due date set.
Dependencies
No dependencies set.
Reference
forgejo-contrib/forgejo-cli#221
WritePreview
Loading…
Add table
| Rows | | | Columns | |
CancelOK
Add a link
Url Description Hint: With a URL in your clipboard, you can paste directly into the editor to create a link.
CancelOK
CancelSave
Reference in a new issue
Repository
forgejo-contrib/forgejo-cli
Title
Body
Create issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
No Yes