Skip to content

Conversation

@lgirdwood
Copy link
Member

Fix
…t -f parsable -d "$yamllint_config" --strict .github/workflows/*.yml *.yml

yamllint -f parsable -d "$yamllint_config" --strict .github/workflows/*.yml *.yml
shell: /usr/bin/bash -e {0}
env:
yamllint_config: {extends: default, rules: {line-length: {max: 100}}}
Warning: orkflows/close-stale.yml:3:1: [warning] truthy value should be one of [false, true] (truthy) Error: Process completed with exit code 2.

Looks like a copy and paste error from:
https://docs.github.com/en/actions/how-tos/use-cases-and-examples/project-management/closing-inactive-issues

Copilot AI review requested due to automatic review settings June 27, 2025 15:03
@lgirdwood lgirdwood requested a review from dbaluta as a code owner June 27, 2025 15:03
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR removes an invalid YAML marker line to resolve a yamllint error in the stale-issue closer workflow.

  • Removed the stray ---- line at the top of .github/workflows/close-stale.yml to satisfy strict YAML linting.

@lgirdwood
Copy link
Member Author

Maybe not

Run yamllint -f parsable -d "$yamllint_config" --strict .github/workflows/*.yml *.yml
Warning: orkflows/close-stale.yml:1:1: [warning] missing document start "---" (document-start)
Warning: orkflows/close-stale.yml:2:1: [warning] truthy value should be one of [false, true] (truthy)
Error: Process completed with exit code 2.

Fixes the following workflow action.

Run yamllint -f parsable -d "$yamllint_config" --strict .github/workflows/*.yml *.yml

yamllint -f parsable -d "$yamllint_config" --strict .github/workflows/*.yml *.yml
  shell: /usr/bin/bash -e {0}
  env:
    yamllint_config: {extends: default, rules: {line-length: {max: 100}}}
Warning: orkflows/close-stale.yml:3:1: [warning] truthy value should be one of [false, true] (truthy)
Error: Process completed with exit code 2.

Signed-off-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
@lgirdwood lgirdwood force-pushed the lrg/topic/gh-actions2 branch from b97d9bc to 3d1f32a Compare June 27, 2025 16:01
@lgirdwood
Copy link
Member Author

Seems to need an update to yamlint (config?) as yml is copied from GH workflows....time for another day....

@lgirdwood lgirdwood closed this Jun 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants