[Question] Documentation or Examples on Custom Actions

[AlbertoVPersonal]

Hi all,

I am looking for detailed documentation or examples on how to use custom actions in SourceGit. Specifically, I need guidance on the following areas:

• How to define and configure custom actions.
• Best practices for implementing custom actions.

Additional Information

• SourceGit Version: 2025.23
• Operating System: Windows 11

Context

I am working on a project where I need to extend SourceGit's functionality by adding custom actions. However, I have not found sufficient documentation or examples to guide me through the process.

Any help or pointers to relevant resources would be greatly appreciated!

Thank you!

[love-linger]

#1160
#1077

[love-linger]

I configured two Custom Actions in my local SourceGit repository:

• Format Codes

Format the codes via dotnet format command.

• Rebuild

Build & publish this project to D:\SourceGit via wt -d "${REPO}" pwsh -NoExit -c "dotnet publish -c Release -o D:\SourceGit src\SourceGit.csproj" command.

[goran-w]

Custom Actions can be created either in the global Preferences or just for a single repo (in the Repository Configure dialog).

A Custom Action can be setup for one of 3 different scopes:

• Repository (triggered via button in main toolbar, variable ${REPO} expands to current repo-path)
• Branch (triggered by right-click on branch, variable ${BRANCH} expands to selected branch)
• Commit (triggered by right-click on commit, variable ${SHA} expands to selected commit)

NOTE: The configured action-command is started in the repository root-folder (i.e ${REPO}).

[goran-w]

TIP: For interaction with remote GH-repos, CLI can be used from Custom Actions.

When contributing to SourceGit I use the following Custom Action, for quickly syncing my fork-repo (remote origin) against the SourceGit main-repo (remote upstream) without having to visit the repo-webpage (or do a reset & push on the local branch) :

This basically does "Fast-forward origin/develop to upstream/develop".
(I added the --force flag just to handle cases where the upstream branch was force-pushed by a maintainer...) 😉