Projects and Profiles

A project is a named group of repositories that you open together. A profile is a set of projects with its own default Git identity, such as one profile for work and one for personal repositories, or one per customer.

Projects and profiles are managed under Settings (Cmd+, on macOS, Ctrl+, on Windows and Linux) → Pro → Projects and profiles.

Create a project

1. Choose New project and enter a Project name.
2. Add repositories with Add repository folder, or enter a Scan folder (absolute path) and choose Scan and add repositories to add every repository under that folder.
3. Optionally choose a Profile, a Git identity, a Default editor, and a Forge connection for the project. Use GitComet editor and Inherit connection keep the defaults.
4. Choose Save project.

One repository in a project can be marked Primary repository with Make primary. Remove from project takes a repository out of the project without touching it on disk.

Choose Open project to open all of the project's repositories in the current window.

Git identity

Commits you make in GitComet Pro use the identity of the project you are working in:

1. the project's own Git name and Git email, if set;
2. otherwise its profile's Default Git name and Default Git email;
3. otherwise your Git configuration, unchanged.

Leave the fields blank to inherit. The bottom bar shows the identity that commits in the current window will use.

Profiles

Choose New profile, enter a Profile name, its default Git identity, and optionally a Forge connection, and choose Save profile. Explore and Review start with the project's forge connection, or the profile's when the project inherits it, and you can still choose another account there. Assign a project to the profile from the project's editor, or leave it Unassigned.

Deleting a profile or a project asks for confirmation. Deleting a project keeps its repositories on disk, and deleting a profile keeps its projects.

Share a project

Export… saves a project as a GitComet project file. Import project… reads one. Before the import is saved, GitComet Pro shows the paths, profile, and Git identity it will use, so you can check them.

Repository paths differ between computers. To fix them in one step, use Move paths from folder: enter the folder the paths start with and the folder To folder they should start with instead, then choose Update matching paths. Each repository's origin URL is saved in the file to help relocate it.