Lines Matching full:changes
147 If the copyright holder for the code you are submitting changes — for example,
158 Changes to Go must be reviewed before they are accepted, no matter who makes the change.
281 Significant changes must go through the
318 of Go installed (some documentation changes may not need this).
338 Most Go installations use a release branch, but new changes should
372 <h3 id="change">Make your changes</h3>
376 Make your changes as you see fit ensuring that you create appropriate
377 tests along with your changes. Test your changes as you go.
407 <h3 id="commit_changes">Commit your changes</h3>
420 Once you have the changes queued up, you will want to commit them.
422 <code>change</code> command, which creates a local branch and commits the changes
428 It is also possible to prepare a sequence of (usually related) changes in a single branch.
438 local branch containing your changes and will not be used elsewhere.
460 # Please enter the commit message for your changes. Lines starting
463 # Changes not staged for commit:
498 # Please enter the commit message for your changes. Lines starting
501 # Changes not staged for commit:
508 It is best to keep unrelated changes in different commits,
535 If you wish to do more editing, re-stage your changes using
544 to update the change description and incorporate the staged changes.
562 tree to make sure the changes don't break other packages or programs:
597 changes to Gerrit using <code>git</code> <code>push</code> <code>origin</code>
612 remote: New Changes:
626 remote: Processing changes: refs: 1, done
669 All changes are automatically CC'ed to the
704 all the changes and comments made in the single URL.
714 stage those changes and use <code>git</code> <code>change</code> to update the
727 You can see a list of your pending changes by running <code>git</code>
735 While you were working, others might have submitted changes to the repository.
752 remote changes into your local changes.
764 Failed to merge in the changes.
803 line: Git failed to merge your changes with the conflicting change.
845 care to preserve your changes, you can run
847 to abandon your changes.
855 As part of the review process reviewers can propose changes directly (in the
858 You can import these changes proposed by someone else into your local Git repository.
865 $ git fetch https://go.googlesource.com/review refs/changes/21/1221/1 && git checkout FETCH_HEAD
886 Since the method used to integrate the changes is "Cherry Pick",
