Show composite action name at step level
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
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:
- Setup a composite action
- Do not give a name to the step when using the composite action
- 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?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the composite action workflow described in the issue, using a step without an explicit name. Trace how the runner labels that step and compare it with the composite action metadata. Done means the displayed step name is taken from the composite action metadata instead of the generic “Run action...” label.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100