The My Accounts menu allows you to register with GitCentric, and set preferences and contact information.
Opening the My Account page
To open the My Account page, choose My Account from the username list:
Profile menu item
Displays a non-editable summary of your user information. You can change the Full Name and Email Address values through the Contact Information option. The Username value shows your AccuRev account name. The Account ID is assigned to you automatically when you register with GitCentric. Note that ID 1000000 is always the first user to register with GitCentric, and is automatically added to the Administrator users group. While the information of the Registered field cannot be modified, its display format can be controlled with the Date/Time Format option under Preferences.
The Preferences page provides access to display and usability options.
|Show Site Header
|Enables/disables the optional header and footer images in your web UI display. For more information, see Get Started.
|Use Flash Clipboard Widget
| When enabled, displays a widget
on various text fields throughout the web UI that allows you to copy the contents of the field to the clipboard.
Note: Requires a Flash-enabled browser.
|CC Me on Comments I Write
|When enabled, you will receive an email containing comments that you submit in response to a review request. The default is to have this setting disabled, to reduce the amount of code review email you receive. But if you want e-mailed confirmation of comments published by your account, you have the option of enabling this setting.
|Display Patch Sets in Reverse Order
|When enabled, reverses the display order of the patch sets in the Change Screen so that the latest patch set is always shown on top. This is useful when there are several patch sets for a change, and the latest patch set and the links to the diffs in the patch set end up below the fold of the Change Screen.
|Display Person Name in Review Category
|When enabled, displays the name of the last reviewer in the “R” column of theGerrit Code Review Dashboard.
|Maximum Page Size
|Specifies the maximum number of rows that will be visible in Gerrit Code Review displays.
|Allows you to specify one of four Date formats (Three American, with month then day, using commas, hyphens, or slashes. One European, with day then month, separated by periods), and one of two Time formats (12 hour AM/PM, or 24 hour).
Watched Repositories menu item
Note: Gerrit Code Review often uses the term Project to refer to a repository. AccuRev uses the terms repository or repo when referring to a repository, and reserves the term project when referring to specific Gerrit functionality, or when referring to some kind of planned or defined undertaking.
The Watched Repositories page allows you to identify the repositories whose changes you want to track.
Click the Add button to add a repository to the Watched Repositories page and to optionally configure Gerrit Code Review to send an email notification whenever a change occurs in that repo.
When adding a repo, use the Browse button to navigate to the repo of interest.
If you want to specify conditions under which you want to be notified of a change (perhaps you are interested only in changes to a specific branch, for example), see the Searching Changes topic in the Gerrit Code Review documentation to learn more about search operations and search expression syntax.
Contact Information menu item
Enter the name of the currently logged-in user. You can register multiple email addresses for this user, but only one can be specified as the preferred address. Gerrit Code Review uses the preferred email address when it needs to generate an email address for you; it uses others to validate incoming email to you.
GitCentric accepts mixed-case values in the email address domain. For example, both
firstname.lastname@example.org are valid email addresses.
You must configure SSH public key authentication before you can upload changes.
If you already have an SSH key:
Click Add and paste the contents of ~/.ssh/id_rsa.pub into the resulting Paste the public SSH Public Key below: field. Make sure that you do not introduce line-breaks when copy and pasting.
If you need to create an SSH key, run install ssh-keygen , a utility normally included as part of a Git or OS installation:
> ssh-keygen -t rsa -C "<yourEmailAddress>@<yourDomain.com>"
For more detailed information about SSH keys, see Before you log in, or follow the link in the dialog box.
AccuRev Servers menu item
Note: Although the UI does not enforce this, you should not specify multiple user accounts on the same AccuRev Server here. If you specify more than one user ID on the same AccuRev Server, GitCentric may default to one that you did not intend. It is fine to specify multiple AccuRev Server here, with one user ID each.
To specify a GitCentric and AccuRev user account association:
- Click the Add button.
- On the panel that appears:
- Select the server from the AccuRev Server list.
- Enter your username on that server in the
AccuRev Username field.
The AccuRev user on this server that you use for GitCentric functions. If you are an administrator, this might be an account like acserver if you have legacy AccuRev systems. See the GitCentric Installation and Release Notes for a discussion about this user account.
- Enter the password associated with that username in the Password field.
- Click the Save button to register the account.
This page describes the HTTP Password options on the My Account page.
Some environments do not permit you to use SSH to connect across a firewall. If you cannot use SSH, but you can connect to the server with smart HTTP, you can generate a password here, and then access your
Git repositories with a URL constructed with
Note: GitCentric supports only Git smart HTTP not so-called dumb HTTP. Smart HTTP is documented on several Git-related sites.
The syntax to clone a repository with smart HTTP is:
git clone http://<username>:<password>@<host>:<port>/p/<repository>
git clone http://testuser:PaoYhDp8BFoA@localhost:8100/p/TestProj2
Once you have cloned, you can pull/push over HTTP just like you can over SSH.
Avoiding password entry
Generated passwords can be difficult to memorize, and providing one each time you connect using HTTP can be a nuisance. Fortunately, Git provides a number of mechanisms to help deal with this.
First, you can create a .netrc file in your home directory (“_netrc” if you are using msysgit on Microsoft Windows). For example:
machine localhost login testuser password PaoYhDp8BfoA
.netrc file lets you keep the
<username>:<password> out of the URL for enhanced security, but it is still stored as plain text.
A more secure approach, if you are using Git 1.7.9 and later, is to use Git’s credential helper, which tells Git to store your password in cache for 15 minutes:
git config --global credential.helper cache
You can increase the timeout by specifying the desired limit in seconds. This example shows the timeout set to 30 minutes:
git config --global credential.helper "cache --timeout=1800"
--unset to revert to specifying the password manually:
git config --unset credential.helper
For more information, see Generate an HTTP password.
People menu option
The People menu item is a read-only display of the security groups to which the logged-in user belongs. To create or modify groups, go to Administration > Groups in the Web GUI. For details about how groups are implemented, see Code Review. For more information, see Manage GitCentric groups.