Lines Matching full:your
11 have <a href="code.html">written and tested your code</a>.
19 <h2 id="Design">Discuss your design</h2>
54 You've <a href="code.html">written and tested your code</a>, but
91 <a href="https://accounts.google.com/SignUpWithoutGmail">with your existing
102 To set up your account in Gerrit, visit
119 Your secret authentication token is now in a <code>.gitcookie</code> file
126 Now that you have your authentication token,
127 you need to register your account with Gerrit.
137 <p>Gerrit serves as the gatekeeper and uses your e-mail address as the key.
138 To send your first change to the Go project from a given address,
147 If your organization is the copyright holder, the organization
151 (If the copyright holder for your code has already completed the
159 or you can show your current agreements and create new ones through the Gerrit
161 click your name in the upper-right, choose "Settings", then select "Agreements"
167 This rigmarole only needs to be done for your first submission for each email address.
181 Make sure <code>git-codereview</code> is installed in your shell path, so that the
232 To install them, copy this text into your Git configuration file
233 (usually <code>.gitconfig</code> in your home directory):
293 If you wish to checkpoint your work, or are ready to send the code out for review, run</p>
300 from any directory in your Go repository to commit the changes so far.
302 local branch containing your changes.
313 Git will open a change description file in your editor.
321 # Please enter the commit message for your changes. Lines starting
331 with a thorough description of your change.
356 # Please enter the commit message for your changes. Lines starting
365 The commented section of the file lists all the modified files in your client.
386 If you wish to do more editing, re-stage your changes using
433 mailing list. If this is your first ever change, there may be a moderation
444 If your change relates to an open issue, please add a comment to the issue
445 announcing your proposed fix, including a link to your CL.
449 The code review server assigns your change an issue number and URL,
492 You can see a list of your pending changes by running <code>git</code>
497 <h3>Synchronize your client</h3>
501 To update your local branch, run
515 remote changes into your local changes.
566 line: Git failed to merge your changes with the conflicting change.
570 It is now your job to edit the file to combine them.
608 care to preserve your changes, you can run
610 to abandon your changes.
618 You can import a change proposed by someone else into your local Git repository.
620 corner, copy the "Checkout" command and run it from your local Git repo.
662 Instead, your name will appear in the
