Skip to main content
Custom Actions lets you bring your own tools into Commit+. Configure an executable or script once, then run it for the current repository, selected files, or selected commits without switching to Terminal. Available starting with Commit+ v1.1.11.

Add a custom action

  1. Open Settings → Custom Actions and click Add.
  2. Enter a Name that describes what the action does.
  3. Choose a Type and configure its executable or script.
  4. Enter any Arguments, using the context placeholders below when needed.
  5. Under Availability, choose Repository, Selected Files, Selected Commits, or a combination.
  6. Enable Always Show Output if you want to see the result after every run, then click Save.

Choose an action type

Scripts support Shell, Bash, Zsh, and Python. Synced scripts must contain UTF-8 text and be no larger than 256 KB. The required interpreter or tool must be available on the Mac where you run the action.

Pass repository and selection context

Commit+ runs each action with the repository as its working directory. Add these placeholders to Arguments to pass the current context to your tool: Placeholders must be standalone arguments. For example, use --repo $REPO, rather than --repo=$REPO. Quote literal arguments that contain spaces, such as "My report". An action using $FILE requires a file selection; one using $SHA requires a commit selection. Match Availability to the context your action needs.

Example: show selected commit details

Create an action with these settings: Select a commit in History and run the action to see its commit message and file change summary in the output sheet.

Run an action

Open the repository you want to work with, then choose an action from Custom Actions:
  • Repository actions are available from Actions → Custom Actions in the menu bar and run with the active repository’s context.
  • File actions appear in the Custom Actions context menu for selected files in File Status.
  • Commit actions appear in the Custom Actions context menu for selected commits in History.
Only actions configured for that context appear. An action is unavailable when a required selection is missing or it has not been trusted on this Mac.

View command output

Enable Always Show Output to inspect successful runs as well as failures. The output sheet shows the action’s status, standard output, and standard error. Failed or cancelled runs show their output automatically. Output is limited to 1 MB per stream; longer output is marked as truncated.

Sync actions across Macs

Open Settings → Custom Actions and enable Sync Custom Actions to sync action definitions across your Macs. You must also have Settings Sync enabled and be signed in to your Commit+ account. Synced definitions include arguments, local paths, and embedded source for Synced Script actions. The Sync Custom Actions toggle applies to the current Mac. Turning it off stops Custom Actions syncing on that Mac; existing cloud copies remain, and your local actions are still available to run. An executable or Local Script file is not uploaded with its definition. Install the tool or copy the script to your other Mac. If its path is missing, use Locate… in Custom Actions settings to select the file on that Mac. Execution trust is local to each Mac. For a synced action that needs approval, click Review…, inspect its executable or script and arguments, then Save. Changes to the command, arguments, or script source require review again on other Macs before execution.
Synced definitions can include script source, arguments, and local paths. Keep credentials and tokens out of these fields.

Manage your actions

Return to Settings → Custom Actions to Edit, Duplicate, or Remove an action. Drag actions in the list to change their order. A Ready status indicates the action is trusted on this Mac and its local file is present when required.