Request GitHub Access¶
You can request GitHub organization access by creating a simple GitHub Issue - it's quick, easy, and creates a clear record of your request.
🎯 Why GitHub Issues?¶
Using GitHub Issues for access requests:
- ✅ Simple and quick - just fill in a template, no forking required
- ✅ Easy to track - clear status updates and discussion
- ✅ No technical barriers - anyone can create an issue
- ✅ Efficient processing - administrators can respond quickly
- ✅ Transparent process - open communication and record-keeping
📋 Prerequisites¶
Before requesting access:
- Completed the quiz with 80% or higher score
- Read all required sections (Getting Started, Basic Rules, Data Safety)
- Have manager approval for GitHub access
- Created GitHub account with your institutional email
- Enabled 2FA on your GitHub account
🚀 Simple 2-Step Process¶
Step 1: Create an Access Request Issue¶
- Click this link: 🎯 Create Access Request Issue →
- Fill in the template that appears automatically
- Click "Submit new issue" - that's it!
Step 2: Wait for Response¶
- Response time: 1-3 business days
- You'll get email notifications when administrators respond
- Status updates will be posted directly in your issue
📝 What Information to Include¶
When you create your issue, you'll need to provide:
Personal Information¶
- Full Name and Department
- Email (institutional email required)
- GitHub Username
- Supervisor name and email
Learning Verification¶
- Completed quiz with 80%+ score
- Read all required documentation sections
- Understand data safety policies
- Have supervisor approval (if required)
Access Justification¶
- What you plan to do with GitHub access
- Specific repositories you need (if known)
- Project or research context
Technical Setup¶
- GitHub account with institutional email
- Two-factor authentication (2FA) enabled
- Profile includes real name and affiliation
Role Requested¶
- Viewer - Read and download access only
- Contributor - Suggest changes via pull requests
- Maintainer - Administrative access (requires additional approval)
📋 Issue Template Preview¶
When you click the link above, you'll see a template like this:
## Personal Information
- **Full Name**:
- **Department**:
- **Email**: [institutional email]
- **GitHub Username**:
- **Supervisor**:
## Learning Verification
- [ ] Completed quiz with score: _%_ (80% minimum required)
- [ ] Read Getting Started guide
- [ ] Read Basic Rules and Data Safety policies
- [ ] Have supervisor approval
## Access Request
**Intended use**: [Describe your planned GitHub activities]
**Specific repositories**: [List any you know about]
**Role requested**: [ ] Viewer [ ] Contributor [ ] Maintainer
## Acknowledgments
- [ ] I will NEVER upload patient/personal data
- [ ] I will NEVER store credentials in GitHub
- [ ] I will follow data classification policies
- [ ] I understand my activity may be monitored
🔍 Review Process¶
What Happens Next¶
- Automated labeling - Your issue gets categorized automatically
- Initial review - Tech managers review completeness within 1 business day
- Supervisor confirmation - We may verify approval with your manager
- Background check - Verify quiz completion and policy understanding
- Account setup - GitHub invitation and role assignment
Timeline¶
- Initial response: Same or next business day
- Complete approval: 1-3 business days
- Complex cases: Up to 1 week (with status updates)
Approval Criteria¶
✅ Complete information in your issue
✅ Quiz passed with 80%+ score
✅ Supervisor approval confirmed
✅ Legitimate business need
✅ Proper technical setup (2FA, institutional email)
🎉 After Approval¶
Once approved:
- GitHub invitation sent to your email
- Role assignment based on your request
- Welcome comment with next steps posted in your issue
- Issue closed with "approved" label
❓ Common Questions¶
"What if I need to update my request?"
Just add a comment to your issue with additional information.
"Can I request access for my team?"
No, each person must submit their own issue to demonstrate understanding.
"What if my request is denied?"
We'll explain why and what to fix. You can create a new issue once ready.
"I'm new to GitHub Issues - is this hard?"
Not at all! It's like filling out a simple form. Much easier than pull requests.
🆘 Getting Help¶
Issue Problems:
- Tag @github-tech-managers in your issue
- Email: GitHub Tech Managers
Policy Questions: - Check our FAQ - Contact: GitHub Tech Managers