question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Show composite action name at step level

See original GitHub issue

Describe the bug Given the use of a custom composite action:

# Composite Action ./.github/actions/build-api/action.yml
name: 'Build API'
description: 'Build the API'
runs:
  using: 'composite'
  steps:
    ...

# Main Workflow
name: Deploy
on:
  push:
    branches:
      - main

jobs:
  deploy:
    name: Build API
    runs-on: ubuntu-latest
    steps:
      - name: Checkout repo code
        uses: actions/checkout@v3
      # Configure Environments
      - uses: ./.github/actions/build-api

The runners do not show the step name of the composite action, instead a generic Run action... step name. Having to update this step name when it can be extracted from the action itself can get tedious when managing lots of actions and workflows.

To Reproduce Steps to reproduce the behavior:

  1. Setup a composite action
  2. Do not give a name to the step when using the composite action
  3. Run the action

Expected behavior The runner shows the name of the composite action for the step taken from the composite action metadata.

Runner Version and Platform

Version of your runner?

OS of the machine running the runner? All

What’s not working?

image

Issue Analytics

  • State:open
  • Created a year ago
  • Reactions:34
  • Comments:8

github_iconTop GitHub Comments

26reactions
AlekSicommented, May 7, 2022

The same can be done for action steps. For example, given that composite action

name: 'Action name'
runs:
  using: 'composite'
  steps:
    - name: Action step 1
      run: go mod download
      working-directory: ${{ github.action_path }}
      shell: bash

I get

image

Both “Action name” and “Action step 1” are not visible. runs.steps.name is a required field, but seems to be unused.

7reactions
anthonwellsjocommented, Mar 29, 2023

Still waiting for this too 🙏 This is a big advantage to be able to create a clean code bases with composite actions, without compromising readability in the UI…

Read more comments on GitHub >

github_iconTop Results From Across the Web

runner/docs/adrs/0549-composite-run-steps.md at main
A composite action is treated as one individual job step (this is known as encapsulation). ... This feature does not support at the...
Read more >
Using if statements in actions
Currently I am just supplying the kubectl version in my workflow, but when the action is triggered it is running all 3 steps...
Read more >
Using Secrets in Composite Actions GitHub
I am creating a composite action and I am trying to use the secrets supplied by GitHub but I am running into errors...
Read more >
Splitting Your GitHub Actions Into Smaller Pieces
Composite actions. A composite action is like a regular workflow file except that it allows you to bundle multiple steps into one action...
Read more >
Composite Actions vs Reusable Workflows
Composite Actions, on the other hand, allow you to pack multiple tasks and operations in a single step, to be reused inside a...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found