feat: github actions extension linter-ignore file and ignore settings
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- github-actions, typescript, vscode
Research direction
No source file or test is named. Start by tracing how the GitHub Actions VS Code extension linter reports errors and how workspace, directory, or user settings are handled. Done means users can suppress selected linter errors through a documented mechanism, with coverage for the chosen ignore behavior.
Written by the indexing model from the issue text.
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.
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
- Dominant language
- TypeScript
- Stars
- 661
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from github/vscode-github-actions
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
github/vscode-github-actions#627 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
github/vscode-github-actions#630 · 1 reaction ·
-
long work Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
github/vscode-github-actions#628 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
github/vscode-github-actions#625 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 64/100
github/vscode-github-actions#621 · 3 comments ·
All issues in github/vscode-github-actions
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
bcgov/bc-wallet-mobile#4761 · 1 comment ·
-
external-issue to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
refactor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100