Silessian
PlanApply for Jira Cloud
PlanApply for Jira Cloud
  • Introduction
    • 🚀About PlanApply for Jira
    • 🛸Features overview
    • 📚Use cases
    • 💿Data structure and processing
    • 💡Workflow
  • Configuration
    • Get started - app configuration
      • 1. Client configuration
      • 2. Submission and provider configuration
      • 3. Remote repositories
  • Global features
    • Designer - getting started
    • 📐Designer
      • Toolbox section
        • Toolbox
        • Templates
        • Import / Export
        • Plan details
        • Submission
        • Collaboration
    • Diagram area
      • Diagram actions
      • Importing objects
      • Adding new elements
      • Updating element details
      • Linking objects
    • 🌏Plan browser
  • Admin features
    • Workspaces
    • Remote repositories
    • Plan browser
    • Terraform console
      • Workspace tab
      • Toolbox tab
      • Terraform tab
        • Generate config
        • Plan
        • Apply
      • Transform tab
    • AI Assistant
    • Execution logs
  • Terraform Provider for Jira Cloud
    • Terraform provider for Jira cloud
      • jira-cloud Provider
      • atlcloudjira_groups (Data Source)
      • atlcloudjira_issues (Data Source)
      • atlcloudjira_users (Data Source)
      • atlcloudjira_customfield (Resource)
      • atlcloudjira_dashboard (Resource)
      • atlcloudjira_field_configuration_scheme (Resource)
      • atlcloudjira_field_configuration (Resource)
      • atlcloudjira_filter (Resource)
      • atlcloudjira_issue_link_type (Resource)
      • atlcloudjira_issue_type_scheme (Resource)
      • atlcloudjira_issue_security_scheme (Resource)
      • atlcloudjira_issue_type_screen_scheme (Resource)
      • atlcloudjira_issue_type (Resource)
      • atlcloudjira_notification_scheme (Resource)
      • atlcloudjira_priority_sequence (Resource)
      • atlcloudjira_permission_scheme (Resource)
      • atlcloudjira_priority (Resource)
      • atlcloudjira_project_component (Resource)
      • atlcloudjira_project_role (Resource)
      • atlcloudjira_project (Resource)
      • atlcloudjira_screen_scheme (Resource)
      • atlcloudjira_screen (Resource)
      • atlcloudjira_status (Resource)
      • atlcloudjira_workflow_scheme (Resource)
      • atlcloudjira_workflow (Resource)
  • Support
    • How to report a bug?
  • 🔓Security statement
Powered by GitBook
On this page
  1. Configuration
  2. Get started - app configuration

3. Remote repositories

Remote git repositories

Previous2. Submission and provider configurationNextDesigner - getting started

Last updated 8 months ago

You can connect given workspace with Git repository. This page allows you to perform the most important operations:

  • Save / Update / Delete settings per workspace

  • Assign git clone command. Git clone command is used to clone entire remote repository to temporary virtual environment and perform other git operations like: status / add / commit / etc.

Example git clone command format:

Git clone command is stored inside Atlassian App Secret storage.

If you need to rotate the token used in string below, replace the entire string and save it again.

git clone https://USER_NAME:APP_TOKEN@bitbucket.org/ORG_NAME/REPO_NAME.git
  1. Select workspace on which you will perform git operation or you want to save / update / delete connection settings.

  2. Git clone command. Must contain username and token. E.g. git clone https://USER_NAME:APP_TOKEN@bitbucket.org/ORG_NAME/REPO_NAME.git

  3. Branch name that will be connected with given workspace.

  4. Save or update git connection settings related to selected workspace. After this workspace will have "Connected" tag in workspace browser.

  5. Delete git connection settings related to selected workspace. After this workspace will have "Not connected" tag in workspace browser.

  6. Based on provider connection and branch setup, repository content will be downloaded into workspace replacing all files.

  7. Based on provider connection and branch setup, repository content will be uploaded into Git repository replacing all files. You can add commit message during the operation.

  8. Based on provider connection and branch setup, workspace content will be compared by 'git status' command with remote repository.

  9. Git operation results will be appearing here.