From d99942f6c54aedcda84fec4bc5f539437c67106a Mon Sep 17 00:00:00 2001
From: Carlo Sala <carlosalag@protonmail.com>
Date: Thu, 23 Jan 2025 21:08:02 +0100
Subject: [PATCH] Update plugins/jira/README.md

---
 plugins/jira/README.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/plugins/jira/README.md b/plugins/jira/README.md
index 794f70607..2b5b86cda 100644
--- a/plugins/jira/README.md
+++ b/plugins/jira/README.md
@@ -44,8 +44,7 @@ This is also checks if the prefix is in the name, and adds it if not, so: "MP-12
 "mp-1234" opens the issue "mp-1234", and "1234" opens the issue "MP-1234".
 
 If your branch naming convention deviates, you can overwrite the jira_branch function to determine and echo the Jira issue key yourself.
-Create a file at `~/.oh-my-zsh/plugins/jira-patch/jira-patch.plugin.zsh` and add `jira-patch` after `jira` in the $plugins variable
-(see https://github.com/ohmyzsh/ohmyzsh/wiki/Customization#partially-overriding-an-existing-plugin).
+Define a function `jira_branch` after sourcing `oh-my-zsh.sh`.
 Example:
 ```zsh
 # Determine branch name from naming convention 'type/KEY-123/description'.