| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Warning
This PR updates start-proxy’s registry-credential filtering so that git_source registries are always enabled, even when credentials are otherwise filtered by language. This aligns with the stated goal that git_source registries can be used by generic workflow components (not only language-specific ones).
Changes:
| File | Description |
|---|---|
| src/start-proxy.ts | Adds an always-enabled registry-type list and updates credential filtering logic accordingly. |
| src/start-proxy.test.ts | Updates/extends tests to validate git_source credentials are always returned across languages. |
| lib/entry-points.js | Generated/excluded by policy (not reviewed). |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This PR changes the language-based registry configuration filtering logic in the start-proxy action to always enable git_source registries since git_source registries are useful outside of language-specific contexts.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Workflow types:
Products:
Environments:
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist