ForkBasetenBasetenpublished Sep 20, 2025seen 5d

basetenlabs/moon-ci-retrospect

forked from appthrust/moon-ci-retrospect

Open original ↗

Captured source

source ↗
published Sep 20, 2025seen 5dcaptured 9hhttp 200method plain

basetenlabs/moon-ci-retrospect

Description: This action is designed for projects using Moonrepo, making the test results of the moon ci command more readable in GitHub Actions logs.

Language: TypeScript

Stars: 0

Forks: 0

Open issues: 3

Created: 2025-09-20T04:10:01Z

Pushed: 2026-05-08T15:27:50Z

Default branch: main

Fork: yes

Parent repository: appthrust/moon-ci-retrospect

Archived: no

README:

appthrust/moon-ci-retrospect

This action is designed for projects using Moonrepo, making the test results of the moon ci command more readable in GitHub Actions logs.

Typically, moon ci executes numerous tasks in parallel, which can make it difficult to view logs in task units. This results in lengthy logs, making it hard to pinpoint the cause of CI failures. This action aims to improve the readability of moon ci results, facilitating easier identification of the reasons for CI failures.

![](./screenshot0.gif)

| ![](./screenshot1.png) | ![](./screenshot2.png) | |------------------------|------------------------| | ![](./screenshot3.png) | ![](./screenshot4.png) |

Usage

jobs:
ci:
name: "CI"
runs-on: "ubuntu-latest"
steps:
- uses: "actions/checkout@v4"
with:
fetch-depth: 0
- uses: "moonrepo/setup-toolchain@v0"
- run: "moon ci --color"
# Add this↓
- uses: appthrust/moon-ci-retrospect@v1
if: success() || failure()

By including this action in your workflow, you can enhance the visibility of test results, making it easier to diagnose and address issues that arise during continuous integration.

Notability

notability 2.0/10

Routine fork, no traction