From 9dd70591c5a05f0b507f2b56ed9660fdd7965420 Mon Sep 17 00:00:00 2001
From: Adam Bender from
- replace `` with
Change-Id: I46f0aec8b7645e2ac8cb53bca73aed55441acd65
Reviewed-on: https://go-review.googlesource.com/42612
Reviewed-by: Brad Fitzpatrick
+
$ git clone https://go.googlesource.com/go
$ cd go
-
+
Once you have the changes queued up, you will want to commit them.
-In the Go contribution workflow this is done with a `git change` command,
-which creates a local branch and commits the changes directly to that local branch.
+In the Go contribution workflow this is done with a git
+change command, which creates a local branch and commits the changes
+directly to that local branch.
@@ -418,9 +419,9 @@ thengitcommit.)-As the `git commit` is the final step, Git will open an editor to ask for a -commit message. -(It uses the editor named by the
$EDITORenvironment variable, +As thegitcommitis the final step, Git will open an +editor to ask for a commit message. (It uses the editor named by +the$EDITORenvironment variable,viby default.) The file will look like: -- 2.52.0