Feature/update-fetch-instructions

README.md

@@ -42,13 +42,12 @@ In the target repository:
 
 - Add this repo as a remote: `git remote add python-release-workflow https://github.com/hpcflow/python-release-workflow.git`
 - Effectively set the remote as fetch-only to avoid accidentally pushing to it: `git remote set-url --push python-release-workflow no-pushing`
-- Fetch all: `git fetch --all`
-- Checkout this repo as a new branch in your repo: `git checkout -b python-release-workflow/main python-release-workflow/main`
-- Checkout the branch you want to synchronise: `git checkout aplowman/develop`
-- Checkout only the `.github` directory from this repository: `git checkout python-release-workflow/main -- .github/`
+- Fetch branches and commits from the `python-release-workflow` repository: `git fetch --python-release-workflow`. Commits to `BRANCHNAME` in `python-release-workflow` will be stored locally in the branch `python-release-workflow/BRANCHNAME`
+- Checkout the branch you want to synchronise workflow updates to: `git checkout aplowman/develop`
+- Checkout only the `.github` directory from the `python-release-workflow` branch of interest: `git checkout python-release-workflow/BRANCHNAME -- .github/`
 - Stage, commit, and push the changes as normal: `git add .github/; git commit -m "build: update GH Actions workflows"; git push`
 
-Note: once the remote is set up and you wish to synchronise again, we can fetch changes like this: `git fetch python-release-workflow main:python-release-workflow/main` (which takes the syntax: `git fetch <remote-name> <src-branch>:<dst-branch>`)
+Note: once the remote is set up and you wish to synchronise again, fetch changes from `python-release-workflow`: `git fetch --python-release-workflow`, and then repeat the checkout, stage, commit and push steps.
 
 
 ## Generating the workflow files from the Jinja2 templates