Skip to content

Conversation

adincebic
Copy link
Contributor

This is very useful for the packages that require form of authentication to clone or download binary artifacts.
It is true that SPM and rules_swift_package_manager work without this if the .netrc file is in $HOME but there are use cases where it is desirable to have .netrc relative to the bazel workspace.

@adincebic adincebic changed the title Support supplying .netrc file feat: Support supplying .netrc file Oct 8, 2025
Copy link
Owner

@cgrindel cgrindel left a comment

Choose a reason for hiding this comment

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

It looks like you need to execute bazel run //:tidy and check in the updated files. I suspect that the test timeouts are not related to your changes.

Can you think of a way to test or exercise this netrc functionality? Could we create a noop .netrc file and then verify that certain behaviors occured?

@cgrindel
Copy link
Owner

cgrindel commented Oct 8, 2025

I forgot to mention. Thank you for the contribution!

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