Confirm organization and repositories
Verify the installation owner and repository selection so that a different Qedix installation is not changed accidentally.
Documentation · Remove access
Remove Qedix safely from GitHub.
An authorized GitHub administrator can reduce repository access or uninstall Qedix. Removing the GitHub App stops future access through that installation, but it is separate from deleting previously stored Qedix records.
Before uninstalling
Prevent repository workflow disruption before removing the GitHub App.
Check branch-protection rules
A repository that requires a Qedix Check may block future pull requests after the app is removed and the check no longer runs.
Notify affected maintainers
Let repository owners know when the review workflow or expected pull-request checks will change.
Decide between reduction and removal
Remove only selected repositories when the organization still needs Qedix elsewhere. Uninstall only when the complete installation should be removed.
Removal steps
Complete these actions in GitHub using an authorized administrator account.
- 01
Confirm the installation
Identify the GitHub organization or account and the repository selection associated with the Qedix installation.
- 02
Review branch protection
Check whether any repository currently requires a Qedix Check before pull requests can merge.
- 03
Open GitHub App settings
Use an authorized GitHub administrator account and open the installed GitHub Apps settings.
- 04
Select Qedix
Open the intended Qedix installation and verify the displayed organization and repositories.
- 05
Reduce or remove access
Remove individual repositories from the selection or use GitHub's uninstall action to remove the complete installation.
- 06
Verify the result
Confirm that the installation no longer includes the removed repositories and update branch-protection expectations where authorized.
What changes after uninstall
Understand the difference between future integration access and historical records.
Future repository access stops
Qedix should no longer receive new installation events or retrieve new repository content through the removed installation.
New Checks stop
Qedix will no longer create or update Checks for future pull-request activity through the removed installation.
Existing GitHub history can remain
Checks, links, and other records previously written to GitHub may remain visible in GitHub history after uninstall.
Existing Qedix records can remain
Previously generated analysis records are not automatically treated as deleted solely because repository access was removed.
Request deletion
Use the Qedix support process for previously stored service records.
Information to include
- GitHub organization or account
- Repository or installation concerned
- Type of records requested for deletion
- Contact method for verification
- Authority to act for the repository
- Any relevant Qedix workspace information
Qedix may require identity, repository, or organization authority verification before acting on a deletion request. Do not include credentials, tokens, private keys, or unnecessary source code.
Branch-protection follow-up
Remove obsolete required-check expectations only through an authorized repository administrator.
Check required status checks
Review repository rulesets and branch-protection settings for a required Qedix Check that can no longer complete.
Preserve review policy intentionally
Replace or remove the check requirement according to your organization's engineering and security policy, not merely to bypass a blocked pull request.