2
24
Fork
You've already forked fgj
4

job log outputing html login page #23

Open
opened 2026年01月14日 02:16:29 +01:00 by mhdali · 2 comments

Hello,

Thank you so much for building this solution up. I'm using it with claude code to seamlessly integrate with my self-hosted Forgejo.

I'm having an issue with running the following command:

fgj actions run view "177" -j "2971" --log

I'm getting the following output (ignore the title as I'm actually invoking the CC to create code that fail the CI):

Title: Test: Break CI with invalid YAML syntax in freshrss
Workflow: dry_run.yml
Run: #177
Status: ✗ failure
Event: push
Ref: test/disposable-break-ci
Commit: 6ca29c13
Created: 2026年01月13日 22:17:19
Started: 2026年01月13日 22:17:20
Updated: 2026年01月13日 22:18:13
========================================
Job: dry-run-roles (ID: 2971)
Status: ✗ failure
========================================
<!DOCTYPE html>
<html lang="en-US" data-theme="forgejo-auto">
<head>
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <title>Sign in - Forgejo: Beyond coding. We Forge.</title>
 <link rel="manifest" href="data:application/json;base64,eyJuYW1lIjoiRm9yZ2VqbyIsInNob3J0X25hbWUiOiJGb3JnZWpvIiw
ic3RhcnRfdXJsIjoiaHR0cHM6Ly9naXQuaG9tZS5hbGZhcnJhLm9yZy8iLCJpY29ucyI6W3sic3JjIjoiaHR0cHM6Ly9naXQuaG9tZS5hbGZhcnJhLm9yZy
9hc3NldHMvaW1nL2xvZ28ucG5nIiwidHlwZSI6ImltYWdlL3BuZyIsInNpemVzIjoiNTEyeDUxMiJ9LHsic3JjIjoiaHR0cHM6Ly9naXQuaG9tZS5hbGZhc
nJhLm9yZy9hc3NldHMvaW1nL2xvZ28uc3ZnIiwidHlwZSI6ImltYWdlL3N2Zyt4bWwiLCJzaXplcyI6IjUxMng1MTIifV19">
 <meta name="author" content="Forgejo – Beyond coding. We forge.">
 <meta name="description" content="Forgejo is a self-hosted lightweight software forge. Easy to install and low
maintenance, it just does the job.">
 <meta name="keywords" content="git,forge,forgejo">
 <meta name="referrer" content="no-referrer">
 <link rel="icon" href="/assets/img/favicon.svg" type="image/svg+xml">
 <link rel="alternate icon" href="/assets/img/favicon.png" type="image/png">
...

Expected output:
The actual log of the failed job.

Version:

  • fgj version: 0.2.0
  • Forgejo Version: 13.0.3

Please help :)

Hello, Thank you so much for building this solution up. I'm using it with claude code to seamlessly integrate with my self-hosted Forgejo. I'm having an issue with running the following command: ``` fgj actions run view "177" -j "2971" --log ``` I'm getting the following output (ignore the title as I'm actually invoking the CC to create code that fail the CI): ``` Title: Test: Break CI with invalid YAML syntax in freshrss Workflow: dry_run.yml Run: #177 Status: ✗ failure Event: push Ref: test/disposable-break-ci Commit: 6ca29c13 Created: 2026年01月13日 22:17:19 Started: 2026年01月13日 22:17:20 Updated: 2026年01月13日 22:18:13 ======================================== Job: dry-run-roles (ID: 2971) Status: ✗ failure ======================================== <!DOCTYPE html> <html lang="en-US" data-theme="forgejo-auto"> <head> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Sign in - Forgejo: Beyond coding. We Forge.</title> <link rel="manifest" href="data:application/json;base64,eyJuYW1lIjoiRm9yZ2VqbyIsInNob3J0X25hbWUiOiJGb3JnZWpvIiw ic3RhcnRfdXJsIjoiaHR0cHM6Ly9naXQuaG9tZS5hbGZhcnJhLm9yZy8iLCJpY29ucyI6W3sic3JjIjoiaHR0cHM6Ly9naXQuaG9tZS5hbGZhcnJhLm9yZy 9hc3NldHMvaW1nL2xvZ28ucG5nIiwidHlwZSI6ImltYWdlL3BuZyIsInNpemVzIjoiNTEyeDUxMiJ9LHsic3JjIjoiaHR0cHM6Ly9naXQuaG9tZS5hbGZhc nJhLm9yZy9hc3NldHMvaW1nL2xvZ28uc3ZnIiwidHlwZSI6ImltYWdlL3N2Zyt4bWwiLCJzaXplcyI6IjUxMng1MTIifV19"> <meta name="author" content="Forgejo – Beyond coding. We forge."> <meta name="description" content="Forgejo is a self-hosted lightweight software forge. Easy to install and low maintenance, it just does the job."> <meta name="keywords" content="git,forge,forgejo"> <meta name="referrer" content="no-referrer"> <link rel="icon" href="/assets/img/favicon.svg" type="image/svg+xml"> <link rel="alternate icon" href="/assets/img/favicon.png" type="image/png"> ... ``` Expected output: The actual log of the failed job. Version: - fgj version: 0.2.0 - Forgejo Version: 13.0.3 Please help :)
romaintb added this to the v0.3.0 milestone 2026年01月16日 10:05:39 +01:00

Hi @mhdali ! Thanks for reporting, I hope to be able to fix that this weekend

Hi @mhdali ! Thanks for reporting, I hope to be able to fix that this weekend

@mhdali, unfortunately, I am not sure we can do something about it, for now.

This feature was implemented about a year ago in Gitea (https://github.com/go-gitea/gitea/pull/33858), but it is not yet backported to Forgejo. I believe the good folks at Forgejo are actively working on CI (v13 and v14 mention the actions with major changes). I can't really contribute to Forgejo as this is way beyond my skills, but feel free to open an issue on their side (just had a quick look and could not find an existing issue mentioning this).

Thanks for reporting this 🙏

@mhdali, unfortunately, I am not sure we can do something about it, for now. This feature was implemented about a year ago in Gitea (https://github.com/go-gitea/gitea/pull/33858), but it is not yet backported to Forgejo. I believe the good folks at Forgejo are actively working on CI (v13 and v14 mention the actions with major changes). I can't really contribute to Forgejo as this is way beyond my skills, but feel free to open an issue on their side (just had a quick look and could not find an existing issue mentioning this). Thanks for reporting this 🙏
romaintb removed this from the v0.3.0 milestone 2026年03月13日 17:59:47 +01:00
Sign in to join this conversation.
No Branch/Tag specified
main
v0.4.0
v0.3.0
v0.2.0
v0.1.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
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
romaintb/fgj#23
Reference in a new issue
romaintb/fgj
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?