Resources
Resources represent connections to git provider workspaces (GitHub organizations or Bitbucket workspaces). Each resource stores the credentials needed to access the provider’s API and clone repositories.
Supported Providers
Section titled “Supported Providers”| Provider | Authentication | Features |
|---|---|---|
| Bitbucket | API token + clone username | Repository import, clone, push, pull request creation, workspace member listing |
| GitHub | GitHub App (installation ID + private key) | Repository import, clone, push, pull request creation |
Creating a Resource
Section titled “Creating a Resource”- Navigate to Resources > New.
- Select your provider.
- Fill in the connection details (see provider-specific fields below).
- Click Save.
ReArch validates the credentials against the provider API before saving. If validation fails, check that your token has the required permissions.
Bitbucket Fields
Section titled “Bitbucket Fields”| Field | Description |
|---|---|
| Name | Display name for this connection. |
| Workspace | The Bitbucket workspace slug. |
| Atlassian account email for API authentication. | |
| Clone Username | Bitbucket username for HTTPS clone operations. |
| API Token | Atlassian API token with repository read/write access. |
GitHub Fields
Section titled “GitHub Fields”| Field | Description |
|---|---|
| Name | Display name for this connection. |
| Organization | The GitHub organization name. |
| Installation ID | The GitHub App installation ID. |
| Private Key | The GitHub App private key (PEM format). |
Managing Repositories
Section titled “Managing Repositories”After creating a resource, import specific repositories from it. See Repositories for the full guide on importing, enabling, configuring templates, and building Docker images.
Editing a Resource
Section titled “Editing a Resource”- Navigate to Resources and click on the resource.
- Update the fields as needed.
- Click Save.
Credential changes take effect immediately for all subsequent API calls and clone operations.
Deleting a Resource
Section titled “Deleting a Resource”Deleting a resource removes the provider connection and all its imported repositories. Existing conversations that reference those repositories continue to function (the container is already running with a cloned copy), but no new conversations can be created for those repositories.