| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
This PR adds support for detecting when the Actions extractor is being used and adjusts the extraction failure logic accordingly. The key change allows the extractor to succeed even when no JavaScript/TypeScript code is found if running in Actions extractor mode.
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| EnvironmentVariables.java | Added constant for Actions extractor environment variable and isActionsExtractor() helper method |
| AutoBuild.java | Updated extraction failure condition to allow Actions extractor to succeed without code, and fixed comment typos |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Sorry, something went wrong.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
The code was written on the assumption that 'seenCode' implies 'seenFiles' but the unit test override 'hasSeenCode()' to always return true. Which meant we would start taking this branch in the unit tests.
There was a problem hiding this comment.
CI looks good for both JS and Actions (manually dispatched).
Sorry, something went wrong.
Actions: don't fail if no JS/TS code was found
…f-no-js Backport: Merge pull request #20752 from asgerf/actions/dont-fail-if-no-js
| Back | FazBrowse Home | New Git URL |
No description provided.