Git, comments, and collaboration
The Git tool manages source-control operations for the project when a checkpoint is available. Connect an authorized remote repository and confirm its host and destination before pushing or importing. Supported remote providers can include GitHub, GitLab, or a self-hosted Git service depending on the configured installation.
Remote setup and synchronization
Review the remote URL, branch, authentication status, and current project checkpoint. Pull or import operations can introduce conflicts; review the proposed changes and target before confirming. A push sends project source to the remote, so verify that no credential or private data is included. If a conflict occurs, keep the conflicting evidence and resolve it in the project rather than force-pushing blindly.
Comments and review handoff
Use project comments to point teammates to a particular file, change, or design decision. Include enough context for another person to reproduce the behavior. Resolve a comment after the change has been reviewed, not merely because it was acknowledged.
Membership and presence
Only members with project access can participate. Presence or member views help identify who is working in the project, but do not replace role checks. For simultaneous editing conflicts, reload the latest state and reapply a small change.
Remote authorization
External Git authorization can expire or be revoked. Reconnect through the supported account or organization flow. Do not enter a personal token into a conversation, source file, or public comment.