If you don’t have git configured on your computer, create a GitHub Personal Access token with at least "repo" scope permissions using these instructions.
GitHub now has two different types of personal access tokens, fine-grained and classic. The above instructions seem to be talking about the classic token, but I believe that GitHub is trying to push more folks to using the fine-grained option as it is the more secure option.
It will be helpful to provide a bit more guidance on which option is preferred by the Platform Team, and to tell users how they should configure their token, such as:
a suggested expiration date, based on input from security folks (this would be helpful for either token type)
if fine-grained is preferred:
which repositories the token needs access to (rather than providing access to all repositories)
[x] Connect with Christopher Floess/Jennifer Brown
[ ] Edit page to include new guidance on GitHub personal access token
[ ] Check for Launch Blocking issues
Acceptance Criteria
[ ] Page is ready for deployment
How to configure this issue
[ ] Attached to a Milestone (when will this be completed?)
[ ] Attached to an Epic (what body of work is this a part of?)
[ ] Labeled with Team (product support, analytics-insights, operations, service-design, Console-Services, tools-fe)
[ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
[ ] Labeled with Type (bug, request, discovery, documentation, etc.)
Issue Description
The docs for configuring the SOCKS Proxy should be updated.
Under "Prerequisites for SOCKS Proxy configuration":
GitHub now has two different types of personal access tokens, fine-grained and classic. The above instructions seem to be talking about the classic token, but I believe that GitHub is trying to push more folks to using the fine-grained option as it is the more secure option.
It will be helpful to provide a bit more guidance on which option is preferred by the Platform Team, and to tell users how they should configure their token, such as:
Relevant URLs
https://depo-platform-documentation.scrollhelp.site/getting-started/accessing-internal-tools-via-socks-proxy
Tasks
Acceptance Criteria
[ ] Page is ready for deployment
How to configure this issue
product support
,analytics-insights
,operations
,service-design
,Console-Services
,tools-fe
)backend
,frontend
,devops
,design
,research
,product
,ia
,qa
,analytics
,contact center
,research
,accessibility
,content
)bug
,request
,discovery
,documentation
, etc.)