Fix super-linter LOG_FILE configuration and remove unnecessary setup steps

[Copilot]

Super Linter's LOG_FILE parameter expects a filename only, not a full path. The workflow was incorrectly configured with /tmp/gh-aw/super-linter.log, causing the linter to fail. Additionally, the super_linter job included unnecessary Go/Node.js setup steps that only the main agent job requires.

Changes

• LOG_FILE configuration: Changed from /tmp/gh-aw/super-linter.log to super-linter.log (filename only)
• Removed setup steps from super_linter job:
  • Set up Go
  • Set up Node.js
  • Install Dependencies (go mod download, npm ci)
  • Create log directory
• Updated path references: All log file references in check-results and upload-artifact steps now use super-linter.log

The super_linter job now only checks out code and runs Super Linter, making it faster and correctly configured.

Original prompt

Fox the super linter configuration with the log file. It has to be a file name, not a path.

https://github.com/githubnext/gh-aw/actions/runs/19182860297

Also the setup install steps are not needed in the superlinter job

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull Request Overview

This PR simplifies the super-linter workflow by removing unnecessary build dependencies and changing the log file path from /tmp/gh-aw/super-linter.log to super-linter.log. The workflow previously set up Go and Node.js build environments that weren't needed since super-linter already includes all necessary linters.

Key Changes:

• Removed Go and Node.js setup steps that were not required for linting operations
• Simplified log file path from /tmp/gh-aw/super-linter.log to super-linter.log
• Eliminated the unnecessary step to create the /tmp/gh-aw directory

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
.github/workflows/super-linter-report.md	Removed unnecessary Go/Node.js setup steps and simplified log file path to use working directory
.github/workflows/super-linter-report.lock.yml	Compiled version of workflow with matching changes to dependencies and log paths

Comments suppressed due to low confidence (2)

.github/workflows/super-linter-report.md:101

• The instructions reference the old log file path /tmp/gh-aw/super-linter.log, but the log file is now written to super-linter.log in the working directory. This mismatch will cause the AI agent to fail when trying to read the log file.

1. **Read the linter output** from `/tmp/gh-aw/super-linter.log` using the bash tool

.github/workflows/super-linter-report.md:80

• The artifact download path still references /tmp/gh-aw/, but the uploaded artifact now contains super-linter.log from the working directory. This creates an inconsistency where the file is downloaded to /tmp/gh-aw/super-linter.log but the instructions in line 101 and the actual upload are based on different paths. The download path should be updated to match the new simplified approach or the instructions should reference the download location.

  - name: Download super-linter log
    uses: actions/download-artifact@v4
    with:
      name: super-linter-log
      path: /tmp/gh-aw/

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.