.\" generated with Ronn-NG/v0.9.1
.\" http://github.com/apjanke/ronn-ng/tree/0.9.1
.TH "GIT\-SED" "1" "November 2023" "" "Git Extras"
.SH "NAME"
\fBgit\-sed\fR \- replace patterns in git\-controlled files
.SH "SYNOPSIS"
\fBgit\-sed\fR [ \-c ] [ \-f \fIflags\fR ] \fIsearch\fR \fIreplacement\fR [ \fIflags\fR ] [ \-\- \fIpathspec\fR ]
.SH "DESCRIPTION"
Run git grep and then send results to sed for replacement with the given flags, if they are provided via \-f or as the third argument\.
.P
Also runs git commit if \-c is provided\.
.SH "OPTIONS"
\-c
.P
commit the resulting changes with a standard commit message detailing the exact command ran\. It will fail if there are unstaged changes\.
.P
<flags> \-f <flags>
.P
will use the given regex flags in the sed command (for example "g" replaces multiple times on the same line)\.
.P
<search>
.P
the pattern passed to grep and to the first part of the sed expression\.
.P
<replacement>
.P
the replacement passed to sed, the second part of the sed expression\.
.P
\-\- <pathspec>
.P
limit the paths which will be applied on\. Read https://git\-scm\.com/docs/gitglossary\.html#Documentation/gitglossary\.txt\-aiddefpathspecapathspec for the supported patterns of pathspec\.
.SH "EXAMPLES"
.nf
$ git sed 'my_function' 'do_stuff'
# \|\.\|\.\|\. only does the changes, without committing
$ git commit \-m"use proper function name"
$ git sed \-c 'do_stuff' 'stuff'
# \.\. does the changes and a commit
$ git sed \-f g do_stuff stuff
# \.\. g is actually pretty important, otherwise you will miss some
# stuff!
$ git sed 'my_method' 'do_stuff' \-\- lake/
# \|\.\|\.\|\. only replace 'my_method' occurs under lake/\.
.fi
.SH "AUTHOR"
Written by Antoine Beaupré <\fIanarcat@debian\.org\fR> from inspiration by https://github\.com/da\-x/git\-search\-replace and https://stackoverflow\.com/questions/9651898/is\-there\-a\-git\-sed\-or\-equivalent
.SH "REPORTING BUGS"
<\fIhttps://github\.com/tj/git\-extras/issues\fR>
.SH "SEE ALSO"
<\fIhttps://github\.com/tj/git\-extras\fR>