github / github/vscode-github-actions

feat: github actions extension linter-ignore file and ignore settings

Open
#414 2 comments 14 reactions 0 assignees View on GitHub
enhancement
Dominant language
TypeScript
Stars
660
Forks
213
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**

In certain GitHub actions, deprecated fields or configurations that are caught by the GitHub actions VSCode extension's linter do still work or exist in certain versions of a GitHub action.

For example, in the screenshot below, the `command: manifest` configuration in Google's release-please GitHub action does still function, but GitHub actions VSCode extension still considers this an error.

![Screenshot 2024-11-04 104641](https://github.com/user-attachments/assets/acb0d73c-1dd9-462b-a90d-7cb2cdf7e3b1)

**Describe the solution you'd like**

I want to be able to add a new comment OR surrounding comments OR a VSCode extension settings file (local to workspace, directory, or user) that will suppress the GitHub actions VSCode extension's linter from highlighting an error.

E.g., adding `// gh-actions-ignore` to a line suppresses the linter, OR adding a `.githubactionsignore` file will allow certain files to go unread by the extension (similar to `.gitignore`), OR a general regex filter in the extensions' VSCode settings

**Additional context**

N/A

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.