sed: -e expression #1, char 10: unknown option to `s' in git on Windows

Question

I am trying to do a simple git commit. I run

git add .
git commit -a -m "Added fixes"

and I get back

sed: -e expression #1, char 10: unknown option to `s'

The solutions I see are for Linux, but unfortunately I'm on Windows (Corporate policy). How can I fix it?

This is the prepare-commit-msg

#!/bin/bash
# Include any branches for which you wish to disable this script
if [ -z "$BRANCHES_TO_SKIP" ]; then
BRANCHES_TO_SKIP=(master develop)
fi
# Get the current branch name and check if it is excluded
BRANCH_NAME=$(git symbolic-ref --short HEAD)
BRANCH_EXCLUDED=$(printf "%s\n" "${BRANCHES_TO_SKIP[@]}" | grep -c "^$BRANCH_NAME$")
# Trim it down to get the parts we're interested in
TRIMMED=$(echo $BRANCH_NAME | sed -e 's:\([a-z]\+\/\)*\([A-Z]\+-[0-9]\+\).\+:\2:')
# If it isn't excluded, preprend the trimmed branch identifier to the given message
if [ -n "$BRANCH_NAME" ] &&  ! [[ $BRANCH_EXCLUDED -eq 1 ]]; then
sed -i.bak -e "1s/^/$TRIMMED: /" $1
fi

If there are hooks installed, you can skip them with https://stackoverflow.com/a/7230886/2295034 — Jonathan.Brink, Sep 04 '19 at 13:33
What's the name branch of your current branch? Does it contain `/`? — Arkadiusz Drabczyk, Sep 04 '19 at 13:47
That's the problem. I get the same error on Linux with GNU sed. — Arkadiusz Drabczyk, Sep 04 '19 at 13:51

score 3 · Accepted Answer · answered Sep 04 '19 at 13:53

3

The problem is that there is / in your branch name but the same character is used in sed script. As a temporary measure, you can replace / in sed script with something else, for example ,:

sed -i.bak -e "1s,^,$TRIMMED: ," $1

In the ideal solution one should look for / in branch name and escape it correctly inside sed script.

answered Sep 04 '19 at 13:53

Arkadiusz Drabczyk

11,227
2
25
38

the / is really important (Jira generated branches). Any idea how I can escape it? – Alex Ironside Sep 04 '19 at 13:56
I don't understand the question. Using the suggested solution you will be able to create a commit and commit message will contain `Fix/SolveCheckButton:` prefix. – Arkadiusz Drabczyk Sep 04 '19 at 13:57
When dealing with pathnames, rather than a `,` sed-`s`-arg separator I like to use `:` – jthill Sep 04 '19 at 15:19
Why `:` specifically? – Arkadiusz Drabczyk Sep 04 '19 at 15:19
Because it's at least conventionally reserved in all filesystems I know of. – jthill Sep 06 '19 at 03:02
On Windows, perhaps. You can easily create a file with a colon in its name on `ext4` on Linux. – Arkadiusz Drabczyk Sep 06 '19 at 09:33
@ArkadiuszDrabczyk that's true, but the colon is for instance used as a separator in all or almost all pathame lists, e.g. `$PATH` is a colon-separated list of directory names, and that's just the top of a long list of commonly-used examples. – jthill Nov 04 '19 at 16:32

sed: -e expression #1, char 10: unknown option to `s' in git on Windows

1 Answers1