handle private GitHub repositories

Open
#270 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github, r
Domain
tooling

Research direction

No file, test, or entry point is named. Start by locating packrat’s existing GitHub repository access path, then compare the proposed devtools and R 3.3.0/libcurl approaches. Done means private GitHub repositories can be accessed with authentication through a documented, tested approach.

Written by the indexing model from the issue text.

Description

Two options:

  1. Implicitly require and use devtools when attempting to access a GitHub repository when possible,
  2. Wait for R 3.3.0 + libcurl and see if we can handle download + authentication there.
Dominant language
R
Stars
409
Forks
89
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rstudio/packrat

All issues in rstudio/packrat

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.