FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Avoid analyzing generated configuration file by henrymercer · Pull Request #2135 · github/codeql-action · GitHub

Avoid analyzing generated configuration file - #2135

Merged
henrymercer merged 1 commit into
mainfrom
henrymercer/no-analyze-config
Feb 13, 2024
Merged

Avoid analyzing generated configuration file#2135
henrymercer merged 1 commit into
mainfrom
henrymercer/no-analyze-config

Conversation

Copy link
Copy Markdown
Contributor

Store the generated config file in temporary directory to prevent it from becoming part of the analysis.

Merge / deployment checklist

  • Confirm this change is backwards compatible with existing workflows.
  • Confirm the readme has been updated if necessary.
  • Confirm the changelog has been updated if necessary.

This prevents it from becoming part of the analysis.
henrymercer requested a review from a team as a code owner February 13, 2024 16:00

angelapwen left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Looks fine, though do we expect the config file to affect the analysis in some way if it's not in the temp directory?

henrymercer commented Feb 13, 2024
edited
Loading

Copy link
Copy Markdown
Contributor Author

Since it's a YAML file it'll be included in JavaScript extraction by default. I noticed when I was trying to create a "no code found" error, but despite no JS or YAML being in the repository, the JavaScript analysis successfully extracted the configuration file and therefore didn't error.

henrymercer merged commit bc64d12 into main Feb 13, 2024
henrymercer deleted the henrymercer/no-analyze-config branch February 13, 2024 18:32
github-actions Bot mentioned this pull request Feb 15, 2024
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
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


Back | FazBrowse Home | New Git URL