GitHub Advanced Usage

1. Log in to GitHub with username_appstate.
2. Click your profile photo and then open Settings.
   
   
   
3. Click on Developer settings at the bottom of the left sidebar.
   
    
4. Open the Personal access tokens drop-down menu and select Tokens (classic).
   
   
   
5. Click the Generate new token drop-down, and select Generate new token (classic).
   
   
   
6. Configure your token:
   • Note: Add a descriptive note detailing what the token is for
   • Expiration: 90 days (recommended) or custom
   • Select scopes:
     • repo - Full repository control
     • workflow - Update GitHub Actions
     • write:packages - Upload packages (if needed)
     • delete:packages - Delete packages (if needed)
7. Click Generate token.
8. Copy the token (you won't see it again).
   

For more detailed guidance, see Managing your Personal Access Tokens.

Clone with HTTPS

git clone https://github.com/username_appstate/repository.git

When prompted:

• Username: username_appstate
• Password: Your PAT (not your actual password)

Store Credentials

Mac/Linux:

git config --global credential.helper cache
# Cache for 1 hour (3600 seconds)
git config --global credential.helper 'cache --timeout=3600'

Windows:

git config --global credential.helper wincred

Update Existing Repository

If you previously used passwords:

git remote set-url origin https://username_appstate:[email protected]/username_appstate/repo.git

Security note: Don't commit tokens in files!

Common Scopes

Minimum Scopes

Basic development: repo
GitHub Actions: repo, workflow
Package management: repo, write:packages, read:packages

GitHub offers fine-grained tokens with repository-specific permissions:

1. Open your Settings, click on Developer settings (at the bottom of the sidebar).
   
   
   
2.  Click on Personal access tokens drop-down and select Fine-grained tokens.
   
   
   
3. Click Generate new token.
   
   
4. Configure your token:
   1. Enter a name and description
   2. Select specific repositories
   3. Choose granular permissions
   4. Set a shorter expiration (recommended).
5. Click Generate Token.
6. Copy the token (you won't see it again).
   

Benefits:

• Repository-specific access
• Detailed permissions
• Better security

For detailed guidance, see Creating a Fine-Grained Personal Access Token.

Open your settings, click on developer settings, and then personal access tokens to see:

• Token names
• Scopes
• Last used
• Expiration dates

1. Click on the token's name, then click Regenerate token.
   
   
   
2. Update everywhere you use it.

Click Delete next to the token to delete it immediately.

DO

• Use descriptive names
• Set expiration dates
• Use the minimum required scopes
• Regenerate regularly
• Use different tokens for different purposes

DON'T

• Share tokens
• Commit tokens to repositories
• Use tokens in client-side code
• Reuse tokens across projects

If the token is exposed

1. Revoke immediately in GitHub settings.
2. Generate a new token.
3. Update all applications.
4. Check for unauthorized access.

Store as repository secret:

1. Repository → Settings → Secrets and variables → Actions
2. New repository secret
3. Name: PAT_TOKEN
4. Use in workflow:

- uses: actions/checkout@v2
  with:
    token: ${{ secrets.PAT_TOKEN }}

Other CI Systems

Store as an environment variable, never in code!

• Verify that the token hasn't expired.
• Check that the token has required scopes
• Ensure you are using the token, not password.

• Check repo scope is selected. 
• Verifiy repository access permissions. 

• Generate a new token.
• Update in all locations.

• Verify the repo scope. 
• Check repository permissions. 
• Confirm token is active.