forgejo-contrib-forgejo-cli-issues-506.md
Watch20
Star402
Fork
You've already forked forgejo-cli
CodeIssues 44Pull requests 8Releases 11Packages 2WikiActivity
Open
opened 2026-06-20 10:57:22 +02:00 by Fluffinity · 1 comment
Fluffinity commented 2026-06-20 10:57:22 +02:00
Contributor
Copy link
For such PRs without CI/CD attached I would expect the fj pr status <pr> command to only return the overall PR status (Open, Closed, Merged) and display that no CI/CD status is available.
forgejo-cli errors out with the following message:
Error: the response from forgejo was not properly structured
Caused by:
unknown variant ``, expected one of `pending`, `success`, `error`, `failure`, `warning` at line 1 column 11
Location:
/<redacted>/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/forgejo-cli-0.5.0/src/prs.rs:706:35
fj pr status <PR number>fj Versionfj v0.5.0
user agent: forgejo-cli/0.5.0 (https://codeberg.org/forgejo-contrib/forgejo-cli/)
build type: crates.io
target: x86_64-unknown-linux-gnu
This also happens with `fj` compiled from main
15.0.0-156-02d7aaa8+gitea-1.22.0
fj pr status \<pr\> command to only return the overall PR status (Open, Closed, Merged) and display that no CI/CD status is available. ### Actual Behavior forgejo-cli errors out with the following message: Error: the response from forgejo was not properly structured Caused by: unknown variant ``, expected one of `pending`, `success`, `error`, `failure`, `warning` at line 1 column 11 Location: /\<redacted\>/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/forgejo-cli-0.5.0/src/prs.rs:706:35 ### Steps to Reproduce 1. Create a new repo without CI/CD on the remote (codeberg.org in this case) 2. Clone the repo 3. Create new branch and checkout 3. Make changes and commit 4. Push new branch to remote and file a PR 5. Invoke fj pr status \<PR number\> ### fj Version text fj v0.5.0 user agent: forgejo-cli/0.5.0 (https://codeberg.org/forgejo-contrib/forgejo-cli/) build type: crates.io target: x86_64-unknown-linux-gnu This also happens with `fj` compiled from main ### Forgejo Version 15.0.0-156-02d7aaa8+gitea-1.22.0 ### 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.Fluffinity added the Kind/Bug label 2026-06-20 10:57:22 +02:00
Fluffinity commented 2026-06-20 11:15:03 +02:00
Author
Contributor
Copy link
In my testing I was able to hunt down the source of that particular error to a missing variant in the CommitStatusState enum in forgejo-api. I will open an issue there with more details. We will need to adjust the code in get_pr_status in prs.rs to handle this edge-case.
In my testing I was able to hunt down the source of that particular error to a missing variant in the CommitStatusState enum in forgejo-api. I will open an issue there with more details. We will need to adjust the code in get_pr_status in prs.rs to handle this edge-case.
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#506
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