View Pipeline Execution Results

Applicable Scenarios: After the pipeline is triggered, you need to confirm the execution status, duration, and final result of each stage (stage) and task, to determine whether the build/test/deployment has been successfully completed.

Configuration Description

Pipeline execution results can be viewed through multiple entry points in the project:

Entry One: Project Homepage → Actions Tab

1. Enter the target project page and click on the Actions tab in the top navigation bar.
2. The left sidebar lists all workflow names; click on the target workflow.
3. The right side displays the list of runs for this workflow, with each record containing:
   • Trigger Event: such as push, pull_request, workflow_dispatch, etc.
   • Trigger Branch/Tag: shows the source of the trigger
   • Status Badge: ✅ Success / ❌ Failure / 🟡 In Progress / ⏸ Cancelled / 🔶 Skipped
   • Run Number: a unique identifier, such as #42
   • Triggered By and Duration

Entry Two: Commit History Page

On the Commits page of the code repository, a simplified status badge is displayed next to each commit record. Clicking it will take you to the corresponding run details.

Entry Three: Pull Request Page

The Checks tab on the PR page aggregates all pipeline execution results triggered by this PR, helping reviewers quickly assess code quality.

Run Details Page

After clicking a run, you enter the details page, whose content depends on the stages structure defined in the workflow:

# View Run Results
stages:
  compile:
    name: build
    jobs:
      - name: compile
        runs-on: {ubuntu-24,x64,small}
        steps:
          - run: make build
  test:
    name: test
    fail_fast: true          # If any job in this stage fails, subsequent stages are skipped
    jobs:
      - name: unit-test
        runs-on: {ubuntu-24,x64,medium}
        steps:
          - run: make test
  deploy:
    name: deploy
    jobs:
      - name: push-image
        runs-on: {ubuntu-24,x64,large}
        steps:
          - run: make deploy

The details page is arranged vertically by stages:

Display Area	Description
Stage Sidebar	Lists each stage in the order defined by stages and indicates their status
Job Card	Displays the name, Runner label, duration, and status of each job
Step Timeline	Shows the execution time and result of each step after expanding a job
Post Processing	If the workflow defines a post stage, it is displayed separately after the main process

Note: AtomGit Action's stages mechanism defaults to sequential execution — the next stage starts only after all jobs in the previous stage succeed. If a stage sets fail_fast: true, then any job failure in that stage immediately stops the current stage and skips all subsequent stages.

Status Badge Embedding

You can embed the run status badge into README:

![Build Status](https://atomgit.com/{owner}/{repo}/badges/{workflow_name}/pipeline.svg)

Common Issues

Q: Why does a certain stage show as "Skipped" in the details page?

A: A job in the preceding stage failed, and the subsequent stage was skipped by the serial execution mechanism; or the preceding stage is configured with fail_fast: true, meaning the entire workflow is terminated if any job fails.

Q: What does the "post" stage appearing in the run details page mean?

A: AtomGit Action supports a post post-processing stage, which by default has run_always: true, so it executes even if the main process fails. It is commonly used for resource cleanup, notification delivery, and similar scenarios.

Q: How to view only failed runs?

A: On the left filter panel of the Actions tab, select the status filter as "Failed".