Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

bug: validate-contribution lint job missing tool setup steps

Open
#19 0 comments 0 reactions 1 assignee View on GitHub

@aRustyDev is already working on this.

Since Jan 27, 2026.

Assessment

This issue has not been assessed yet.

Description

bug

Problem

The atomic-release-validate-contribution.yml reusable workflow has a lint_setup_steps input parameter that is defined but never used. The lint job runs lint_command directly without any setup, causing failures when the command requires tools that aren't pre-installed.

Current Implementation

inputs:
  lint_setup_steps:
    description: 'JSON array of setup steps to run before linting'
    required: false
    type: string
    default: '[]'

But the lint job never references this input:

lint:
  steps:
    - name: Checkout
      uses: actions/checkout@v4
    - name: Run lint command  # No setup steps\!
      run: |
        eval "${{ inputs.lint_command }}"

Impact

When lint_command is ct lint --config ct.yaml, the job fails with:

##[error]Process completed with exit code 127.

(command not found)

Workaround

Consumers must implement their own local lint job with proper setup:

  • azure/setup-helm@v4
  • actions/setup-python@v6
  • helm/chart-testing-action@v2.7.0

Proposed Fix

Either:

  1. Implement lint_setup_steps: Parse the JSON array and run setup actions before lint
  2. Remove the input: If setup can't be dynamic, remove the misleading parameter
  3. Document the limitation: Clearly state that lint_command must use pre-installed tools

Discovered

  • E2E-1 testing on 2026-01-26
  • Consumer: aRustyDev/helm-charts
Dominant language
Shell
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aRustyDev/gh

All issues in aRustyDev/gh

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.