general-settings

GitHub Token

The GitHub token is used to authenticate with GitHub and retrieve:

  • Repositories
  • Issues
  • Pull Requests
  • Comments and reactions

This token is required for repository integration features. For more information on creating a GitHub Token, check out their documentation.

Token Permissions

Ensure your token has the following scopes:

  • repo - Full control of private repositories (for accessing private repos)
  • read:user - Read user profile data

Timeout Settings

Mule uses several timeout settings to control workflow and request execution:

timeout_workflow_seconds

Controls the maximum execution time for a single workflow step.

  • Default: 300 (5 minutes)
  • Type: Integer (seconds)
  • Used by: Workflow engine for step execution timeout

timeout_request_seconds

Controls the maximum time for HTTP requests to the API server.

  • Default: timeout_workflow_seconds + 60 seconds
  • Type: Integer (seconds)
  • Used by: API server request timeout middleware

timeout_job_seconds

Controls the maximum execution time for an entire job (workflow with all steps).

  • Default: 3600 (1 hour)
  • Type: Integer (seconds)
  • Used by: Job execution context timeout

Repository Cloning

Mule supports repository cloning through WASM modules. The git-worktree module can clone repositories and create isolated worktrees for parallel development:

{
  "operation": "clone_and_worktree",
  "repo_url": "https://github.com/owner/repo.git",
  "worktree_name": "mule/issue-42",
  "token": "{{GITHUB_TOKEN}}"
}

For SSH-based cloning, ensure SSH keys are configured on the system where Mule is running. The GitHub token can also be used for HTTPS cloning with authentication.

Future Features

Additional configuration options may include:

  • Built-in repository management UI
  • Automatic repository sync scheduling
  • Enhanced webhook support

See the Mule project for the latest developments.

Was this page helpful?