Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use native node fetch API instead of node-fetch module #318

Open
hinricht opened this issue Apr 25, 2024 · 0 comments
Open

Use native node fetch API instead of node-fetch module #318

hinricht opened this issue Apr 25, 2024 · 0 comments

Comments

@hinricht
Copy link

Issue Report

Please use native node fetch API instead of node-fetch module.
We use repolinter and include a remote config via `extends, and are behind a coorporate Proxy, and node-fetch doesn't support proxy configurations.
We need to jump through several burning hoops to make it working (using proxychains i.e.).

Expected Behavior

We can use repolinter without any custom workaround behind a cooperate proxy and can include a remote config.

Actual Behavior

Repolinter: FAIL!
Linting repository "/Users/dj/repolintertest/genesis" with repolinter and pre-commit-tools image tag: 0.5.0
FetchError: request to https://raw.githubusercontent.com/todogroup/repolinter/main/rulesets/default.json failed, reason:

Steps to Reproduce the Issue

  • Find a place with a (coorporate) proxy
  • Export proxy env vars as usual
  • Use this config
extends: https://raw.githubusercontent.com/todogroup/repolinter/main/rulesets/default.json
  • Run repolinter

Additional resources

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

No branches or pull requests

1 participant