Evidence scope: Steps are traced to MonkeyCode source at
2a7f2d48f6ebe963fafb0d363680329204f9bbe1and GitHub’s official documentation, checked September 8. This site has not yet completed a hosted-account connection and revocation test.
1. Start with a repository you control
Download the first-task starter, create a new repository in your own GitHub account and add only those example files. GitHub sign-in and repository installation are different permissions: being signed in is not proof that a task can clone a repository.
2. Connect the Git identity
Open MonkeyCode settings and the Git identities section. The reviewed source offers a GitHub connection that opens the GitHub App installation flow. Check the app identity and requested permissions on GitHub, select your intended account, choose Only select repositories, and select the example repository. Organization repositories may need an owner’s approval.
Return to MonkeyCode and confirm that the Git identity appears. The source’s English labels include “Git identities”; the currently deployed edition may use different or Chinese labels. This describes the source path, not a recorded successful click sequence.
3. Create the project
Open Create project, enter Project name, select the connected identity, then Select repository. Confirm the exact owner and repository before submitting. The reviewed code requires those selections and navigates to the created project after success.
Run the starter’s baseline command in the task environment. Expect one intentional failure among eight tests. This verifies the code actually reached the environment; a connection badge alone does not.
4. If the repository is missing
Check the selected GitHub account, the app’s installation owner and repository selection. For an organization, check approval status. Return to MonkeyCode and refresh the repository selection after GitHub changes. Do not grant all repositories just to hide an authorization problem.
5. Revoke at both layers
First stop example tasks that still need access. In GitHub, use Settings → Applications → Installed GitHub Apps → Configure for the relevant installation. Remove the example repository, suspend the installation, or uninstall it depending on the intended scope. Organization settings manage organization-owned installations.
If you also want to stop the app acting as your user, revoke its entry under Authorized GitHub Apps. If an older flow used an OAuth app, review Authorized OAuth Apps separately. Back in MonkeyCode, remove the corresponding Git identity in settings; its source performs a local identity deletion, which alone does not prove the GitHub grant was revoked.
Finally attempt a new authenticated repository operation and record whether it is denied. Existing clones and task outputs may remain readable; a public repository may still clone anonymously. Neither observation disproves nor proves credential revocation. Verify the account’s grant list as well. Continue with the task exercise.