Skip to content
This repository has been archived by the owner on Sep 9, 2020. It is now read-only.

Modify FAQ.md to address http authentication with git #822

Closed
wants to merge 1 commit into from
Closed

Modify FAQ.md to address http authentication with git #822

wants to merge 1 commit into from

Conversation

matjam
Copy link
Contributor

@matjam matjam commented Jul 15, 2017

Added instructions for authentication with git to the FAQ.

What does this do / why do we need it?

Clarify #264

What should your reviewer look out for in this PR?

Make sure that the examples work as expected.

Do you need help or clarification on anything?

Which issue(s) does this PR fix?

fixes #264

Added instructions for authentication with git.
@googlebot
Copy link
Collaborator

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If your company signed a CLA, they designated a Point of Contact who decides which employees are authorized to participate. You may need to contact the Point of Contact for your company and ask to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the project maintainer to go/cla#troubleshoot.
  • In order to pass this check, please resolve this problem and have the pull request author add another comment and the bot will run again.

@matjam matjam changed the title Modify FAQ.md Modify FAQ.md to address http authentication with git Jul 15, 2017
@matjam
Copy link
Contributor Author

matjam commented Jul 15, 2017

I signed it!

@googlebot
Copy link
Collaborator

CLAs look good, thanks!

Copy link
Member

@sdboyer sdboyer left a comment

Choose a reason for hiding this comment

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

just two nits. again, thank you, i'm so grateful you tracked this down!

@@ -121,6 +122,42 @@ No.
> We prefer to treat the `vendor/` as an implementation detail.
-[@sdboyer on go package management list](https://groups.google.com/d/msg/go-package-management/et1qFUjrkP4/LQFCHP4WBQAJ)

## How do I get dep to authenticate to a git repo?

dep currently uses the git command under the hood, so configuring the credentials
Copy link
Member

Choose a reason for hiding this comment

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

consistency nit: backticks around git, dep, etc.


After configuring git, you may need to use git manually once to have it store the
credentials. Once you've checked out the repo manually, it will then use the stored
credentials. This at least appears to be the behaviour for the osxkeychain.
Copy link
Member

Choose a reason for hiding this comment

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

more consistency nits: American English spellings, please 😄

@matjam
Copy link
Contributor Author

matjam commented Jul 18, 2017

I'll make a new PR with the suggested changes.

@matjam matjam closed this Jul 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Http authentication for private repositories
3 participants