Composite Actions: Give users control over how verbose the step output is
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
No output grouping on composite actions
To Reproduce
Create a composite action that uses log grouping with echo "::group::Start.." echo "::endgroup::"
name: 'Issue'
description: 'Composite example'
inputs:
ruby-version:
description: 'Ruby version'
required: false
default: '2.6.0'
runs:
using: "composite"
steps:
- name: Setup rbenv
run: |
echo "::group::Installing rbenv..."
brew list rbenv || brew install rbenv
echo "~/.rbenv/shims" >> $GITHUB_PATH
echo "::endgroup::"
shell: bash
- name: Setup Ruby
run: |
echo "::group::Setting up ruby environment..."
rbenv install ${{ inputs.ruby-version }} -s
rbenv local ${{ inputs.ruby-version }}
rbenv rehash
which ruby
rbenv which ruby
echo "::endgroup::"
shell: bash
- name: Bundle Install
run: |
echo "::group::Running bundle install..."
gem env home
gem install bundle
bundle install
echo "::endgroup::"
shell: bash
Using this composite action on another action has the following output:
Prepare all required actions
➤ Run ./.github/actions/issue
➤ Run echo "::group::Installing rbenv..."
➤ Installing rbenv...
➤ Run echo "::group::Setting up ruby environment..."
➤ Setting up ruby environment...
➤ Run echo "::group::Running bundle install..."
➤ Running bundle install...
Expected behavior
Prepare all required actions
➤ Run ./.github/actions/issue
➤ Installing rbenv...
➤ Setting up ruby environment...
➤ Running bundle install...
This was the output of a job running on '2.280.3'
Runner Version and Platform
Version of your runner?
2.281.1
OS of the machine running the runner?
OSX
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 tracing composite action execution and how the runner handles group commands in the displayed step output; the issue provides a reproducible YAML action and expected versus actual logs. Verify behavior on the referenced runner versions and OSX, and consider the work complete when composite-action groups produce the expected collapsed output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github-actions
- Domain
- ci-cd, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100