Skip to content

Matrix jobs are not grouped in the run graph when name: is set #38975

Description

@bircni

Gitea Version

1.27.2

What happened?

The run graph collapses matrix legs into a single Matrix: <job-id> box only when Gitea
derived the job's display name itself. If the workflow sets name: on the job, the legs
are rendered as individual nodes and no grouping box appears — even when the supplied name
has exactly the same shape as the derived one.

Steps to reproduce

on: workflow_dispatch
jobs:
  derived:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        leg: [one, two]
    steps:
      - run: echo "${{ matrix.leg }}"

  explicit:
    name: "explicit (${{ matrix.leg }})"   # same shape Gitea would generate
    runs-on: ubuntu-latest
    strategy:
      matrix:
        leg: [one, two]
    steps:
      - run: echo "${{ matrix.leg }}"

Dispatch it and open the run graph.

Actual

  • derived → one box: Matrix: derived — 2 jobs completed / Show all jobs
  • explicit → two separate nodes, explicit (one) and explicit (two), no grouping box

Expected

Both are matrix jobs and both should group. The legs share a job id in either case, and
setting name: is documented as controlling the display name, not the job's identity.
GitHub's UI groups matrix legs under the job regardless of whether name: is set.

How are you running Gitea?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions