Skip to main content

Git Credentials in AIQ

Use Git credentials in AIQ only for approved repository access. Credentials should be scoped, rotated, and stored through approved mechanisms instead of being copied into scenario steps, documentation, logs, or shared screenshots.

Credential options

  • Personal access tokens or service-account tokens approved for automation.
  • SSH keys managed by the repository owner or platform team.
  • Read-only access when AIQ only needs to pull repository content.
  • Write access only when the workflow explicitly requires AIQ to push changes.

Security checklist

  1. Confirm the repository, branch, project, and required access level.
  2. Use least privilege and avoid broad organization-level access.
  3. Document owner, expiration, rotation, and revocation process.
  4. Test repository connectivity without exposing the credential value.
  5. Remove old credentials when users leave or repository ownership changes.

Last updated: October 6, 2026

Back to top