Branch Protection State - 2026-09-20T00:28:28.536Z
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
{
"url": "https://api.github.com/repos/gitpod-io/gitpod/branches/main/protection",
"required_status_checks": {
"url": "https://api.github.com/repos/gitpod-io/gitpod/branches/main/protection/required_status_checks",
"strict": false,
"contexts": [
"Build Gitpod"
],
"contexts_url": "https://api.github.com/repos/gitpod-io/gitpod/branches/main/protection/required_status_checks/contexts",
"checks": [
{
"context": "Build Gitpod",
"app_id": 15368
}
]
},
"required_pull_request_reviews": {
"url": "https://api.github.com/repos/gitpod-io/gitpod/branches/main/protection/required_pull_request_reviews",
"dismiss_stale_reviews": false,
"require_code_owner_reviews": true,
"require_last_push_approval": false,
"required_approving_review_count": 1
},
"required_signatures": {
"url": "https://api.github.com/repos/gitpod-io/gitpod/branches/main/protection/required_signatures",
"enabled": false
},
"enforce_admins": {
"url": "https://api.github.com/repos/gitpod-io/gitpod/branches/main/protection/enforce_admins",
"enabled": true
},
"required_linear_history": {
"enabled": true
},
"allow_force_pushes": {
"enabled": false
},
"allow_deletions": {
"enabled": false
},
"block_creations": {
"enabled": false
},
"required_conversation_resolution": {
"enabled": false
},
"lock_branch": {
"enabled": false
},
"allow_fork_syncing": {
"enabled": false
}
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue contains only a generated GitHub branch-protection JSON snapshot for the main branch; it names no repository files, tests, or entry points. Start by determining why this snapshot was created and what change is expected, then define a concrete success condition before attempting implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100