Secure Authentication

Security Education Required

Before entering any tokens, you must study and acknowledge the security requirements below. This ensures you understand how to protect your GitHub account.

Security Knowledge Check

Please read and acknowledge all security requirements below. Token entry will remain locked until all conditions are accepted.

๐Ÿ”’ Token entry locked - Complete security acknowledgment

Security Reminders

1. Create token with 1-day expiration for maximum security

2. Select ONLY required permissions (repo scope minimum)

3. Delete token from GitHub immediately after use

4. Never share tokens or commit them to repositories

Operation Configuration

Best Practices

Always test operations on a single repository first. Review GitHub API rate limits before bulk operations.

Target Repositories

Upload .txt or .csv file with repository list

Collaborator Management

Upload .txt or .csv file with usernames

Verify GitHub Users

Search for GitHub users to verify their existence and view their public repositories.

Verification Benefits

  • Verify GitHub usernames exist before adding as collaborators
  • View user's public repositories
  • Auto-add verified users to collaborator list
  • Prevent errors from invalid usernames

Operation Audit Log

Security-first session initialized
Token entry locked until security acknowledgment complete
Please study the security guide and complete acknowledgment