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

Invalid warnings in problems for Github Actions YML

Open
  • Is something wrong?
#463 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd, tooling

Research direction

Start by reproducing the VS Code Problems warning with the close_pull_request workflow shown, especially the Azure/static-web-apps-deploy@v1 step using action: "close". Trace how this workflow is validated and confirm that a valid close workflow no longer reports missing app_location; the issue names no test file.

Written by the indexing model from the issue text.

Description

bug

Describe the bug
This bug was originally created in this repo : https://github.com/microsoft/GitHub-Copilot-for-Azure/issues/206 by accident

Missing required input app_location keeps appearing when it's missing from close pull request action:
close_pull_request_job:
if: github.event_name == 'pull_request' && github.event.action == 'closed'
runs-on: ubuntu-latest
name: Close Pull Request Job
steps:

  • name: Close Pull Request
    id: closepullrequest
    uses: Azure/static-web-apps-deploy@v1
    with:
    azure_static_web_apps_api_token: ${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN}}
    action: "close"

To Reproduce
Steps to reproduce the behavior:

  1. With this workflow '...'
  2. Do this '...'
  3. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Extension Version
v1.x.y

Additional context
Add any other context about the problem here.

CC : Original user : aviscoreTH

Dominant language
TypeScript
Stars
661
Forks
214
No merged PRs in 30d

Getting set up

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 github/vscode-github-actions

All issues in github/vscode-github-actions

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.