Get Zulipnotifications for yourGitrepositories!

1. {!download-python-bindings.md!}

Note that Zulip also offers integrations for[GitHub](./github),

[GitLab](./gitlab) and various other

[version control hosting services][other-integrations].

1. {!create-channel.md!}

{start_tabs}

1.{!change-zulip-config-file.md!}

1. {!create-an-incoming-webhook.md!}

You can specify the branches that will be used for notifications by modifying

the`commit_notice_destination` function. By default,

pushes to the`main`,`master`, and`test-post-receive` branches will result in a

notification.

1. If your Git server and your Zulip server are on the same machine,

symlink the`post-receive` hook of your Git repository in your Git

server by running:

1. Symlink`/usr/local/share/zulip/integrations/git/zulip_git_config.py`

to the`.git/hooks` directory of your Git repository.

1. Symlink`/usr/local/share/zulip/integrations/git/post-receive`

to the`.git/hooks` directory of your Git repository.

Otherwise, copy the`post-receive` hook to your Git repository's

`/hooks` directory.

The`post-receive` hook is triggered on every push to the repository.

1. {!change-zulip-config-file.md!}

1. Copy the config file to the same directory as the`post-receive` hook.

!!! tip ""

{end_tabs}

In`{{ config_file_path }}`, you can set:

- The channel where notifications are sent by updating the value of

`STREAM_NAME`. By default, notifications are sent to a channel named

"commits".

- Which branches send notifications when pushed by updating the

`commit_notice_destination` function. By default, pushes to the`main`,

`master`, and`test-post-receive` branches will result in notifications.

{!congrats.md!}

- The message format used in your Zulip notifications by updating the

`format_commit_message` function.