forgejo-contrib/forgejo-cli
20
408
Fork
You've already forked forgejo-cli
51

fj pr checkout does not set upstream #460

Open
opened 2026年05月11日 18:28:00 +02:00 by ncf · 0 comments

Expected Behavior

fj pr checkout 42 should set the branch's tracking information so that one can pull later changes by doing git pull (and edit the branch with git push).

Actual Behavior

It does not. I have to recreate the branch from scratch, which is impractical because of #439 (I need to first switch to a different branch with a correct upstream, then run fj pr checkout again).

fj Version

fj v0.4.1
user agent: forgejo-cli/0.4.1 (https://codeberg.org/forgejo-contrib/forgejo-cli/)
build type: nixpkgs
 target: x86_64-unknown-linux-gnu

Forgejo Version

No response

Code of Conduct

  • I agree to act in accordance with the CoC & AI Agreement.
  • This issue was not generated by an LLM, even in part.
### Expected Behavior `fj pr checkout 42` should set the branch's tracking information so that one can pull later changes by doing `git pull` (and edit the branch with `git push`). ### Actual Behavior It does not. I have to recreate the branch from scratch, which is impractical because of https://codeberg.org/forgejo-contrib/forgejo-cli/issues/439 (I need to first switch to a different branch with a correct upstream, then run `fj pr checkout` again). ### `fj` Version ```text fj v0.4.1 user agent: forgejo-cli/0.4.1 (https://codeberg.org/forgejo-contrib/forgejo-cli/) build type: nixpkgs target: x86_64-unknown-linux-gnu ``` ### Forgejo Version _No response_ ### Code of Conduct - [x] I agree to act in accordance with the CoC & AI Agreement. - [x] This issue was not generated by an LLM, even in part.
Sign in to join this conversation.
No Branch/Tag specified
main
renovate/open-5.x-lockfile
renovate/comrak-0.x
renovate/uuid-1.x-lockfile
renovate/lock-file-maintenance
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
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#460
Reference in a new issue
forgejo-contrib/forgejo-cli
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?