📖
Typo Help Docs
  • Welcome
  • Getting Started
    • Onboarding
    • Integrations
      • Git
        • GitHub
        • GitLab
        • BitBucket
        • Azure Repos
        • Gitlab On-prem
      • Issue Tracker
        • JIRA
        • Linear
        • GitHub Issue
        • Shortcut
        • ClickUp
      • CI/CD Tool
        • Circle CI
        • Jenkins
        • Heroku
        • GitHub Actions
        • Azure DevOps
        • Custom Deployment Webhook
      • Slack
    • How Requestly setup Typo in a few days
  • Platform
    • Dev Analytics
      • DORA
      • Insights
        • Teams
        • Members
        • Sprints
        • Pull Requests
        • Deployments
      • Incident
      • Goals
      • Investment
      • Initiative
      • WorkLog
      • Custom Reports
      • Settings
        • Teams
        • Member
        • Repository
        • Projects
        • Manage Access
        • Notifications
    • Code Health
      • Code Review
      • Code Coverage
    • DevEx
  • Implementation Plan
    • Phase 1 - Setting Up Data Sources
    • Phase 2 - Metric Configuration
      • Dev360
      • Code Health
      • DevEx
    • Phase 3 - Team Rollout
  • Engineering Metrics
    • DORA
      • Cycle Time
      • Deployment PRs
      • Change Failure Rate
      • Mean Time to Restore
    • Pull Request Metrics
      • Avg. Commits During PR Review
      • Coding Days
      • Coding Time
      • Merge frequency
      • Merge Time
      • Pickup Time
      • PR Size
      • PRs Merged without Review
      • Review Time
      • Efficiency Score
    • Sprint Metrics
      • Carry over
      • Developer Workload
      • Issue Cycle Time
      • Issues At-Risk
      • Scope creep
      • Team Velocity
      • Work Breakup
      • Work Progress
    • Code Quality Metrics
      • OWASP Top 10
      • Vulnerability
      • Security
      • Performance
      • Duplication
      • Code Smell
    • Deployment Metrics
      • Deployment - Failure
      • Deployment - Frequency
      • Time to Build
    • Incident Metrics
      • Incident - Opened
      • Avg Resolution Time
    • DevEx Metrics
      • DevEx Score
      • Space mood
      • Response Rate
      • Manager Support
      • Developer Flow
      • Product Management
      • Development & Releases
      • Culture & Values
  • Configurations
    • Cycle Time
    • Deployment PRs
    • Change Failure Rate (CFR)
    • Mean Time To Restore (MTTR)
    • CI/CD - Deployment
    • Incident
    • Initiative
    • Investment Distribution
    • PR Labels
    • Code Health
    • Code Coverage
    • DevEx
    • Notifications
    • Manage Access
  • FAQ's
    • Data Security
      • GitHub App Permissions Details
      • Why does Typo need write permission to my code?
      • Does Typo has access to my code?
      • What data security guidelines does Typo follow?
    • Integrations
      • Can Typo application work with on-prem Gitlab?
      • How do I get Issue Tracker data?
      • How do I get Git data?
    • Pricing
      • How does the pricing work?
      • How do I upgrade my plan?
    • Access Management
      • My team member is not able to login to Typo
    • Metrics
      • How does Typo predict developer burnout?
      • Is there a way to change the branch that Deployment PRs are measured against?
      • Synchronize “CFR” & “MTTR” without incident management?
      • How quick does the pull-request page update? I closed a PR but the Typo still shows Awaiting Review
      • How do I add any new repo?
      • How to Configure Typo Code Health Checks to Block a PR Merge in Git
      • Can I exclude a person from metrics calculation?
      • Can I track the Cycle time based on the status of the JIRA tickets?
      • How do I unlink the JIRA tracker & integrate Linear?
      • How to exclude a PR from any metric calculation?
      • My data is not visible, I have synced the repo
    • Platform
      • Can I use your application on-premise?
    • Delete Account
      • How can I delete my account?
Powered by GitBook
On this page
  • DEV 360 Github Permissions
  • Repository permissions
  • Organization permissions
  • Account permissions
  • Code Health Github Permissions
  • Repository permissions
  1. FAQ's
  2. Data Security

GitHub App Permissions Details

DEV 360 Github Permissions

Repository permissions

Repository permissions permit access to repositories and related resources.

Actions (Read only)

This permission allows access to the results of workflow and job runs. Typo uses this permission to read the results of workflow and job runs to show the Deployment Frequency

Issues (Read and write)

This permission includes access to issues and related comments, assignees, labels, and milestones. Typo uses this permission to read and write comments on pull requests.

Metadata (Read-only)

This permission includes access to search repositories, list collaborators, and access repository metadata. This permission is required by all GitHub applications that access repository information.

Pull requests (Read and write)

This permission includes access to pull requests and merges. Typo uses this permission to view all the information related to a pull request and approve/merge pull requests.

Project (Read only)

This permission allows access to the results of classic projects within a repository. Typo uses this permission to read all the GitHub Projects and its issues to use it as an issue tracker.

Organization permissions

Organization permissions permit access to organization-related resources.

Members (Read-only)

This permission includes access to organization members and teams. Typo uses this permission to get all the information about the organization's members and teams to show in the dashboard. Project (Read-only) This permission allows access to an organization's project results. Typo uses this permission to read all the GitHub Projects and issues to use them as an issue tracker.

Account permissions

These permissions are granted on an individual user basis as part of the User authorization flow.

Email addresses (Read-only)

This permission includes access to the users' email addresses. If enabled, Typo uses this permission to access users' email addresses for any type of communication.

Code Health Github Permissions

Repository permissions

Repository permissions permit access to repositories and related resources.

Commit statuses (Read Only)

This permission allows access to the commit statuses. Typo uses this permission to read the commit statuses and update them according to the Pull Request Issues raised for that branch.

Content (Read and write)

This permission includes access to contents, commits, branches, downloads, releases, and merges for a repository. Typo uses this permission to read the repository's contents to raise code health issues and create an autofix Pull Request if required by the user.

Issues (Read and write)

This permission includes access to issues, related comments, assignees, labels, and milestones. Typo uses this permission to read and write comments on pull requests.

Metadata (Read-only)

This permission includes access to search repositories, list collaborators, and access repository metadata. This permission is required by all GitHub applications that access repository information.

Pull requests (Read and write)

This permission includes access to pull requests and merges. Typo uses this permission to read the content of a pull request and update the description of a pull request by adding the PR summary.

Workflows (Read and write)

This permission allows access to update GitHub Action workflow files. Typo uses this permission to integrate code coverage with GitHub Actions

PreviousData SecurityNextWhy does Typo need write permission to my code?

Last updated 3 months ago