Doc downloads (PDF, HTML & XML)
[FishEye Knowledge Base]
The commit graph shows changesets in their respective branches, using configurable "swimlanes". This allows you to see key information such as branching and merging (and if you are using Git or Mercurial, you will be able to see anonymous branches as well).
The Highlight feature of the commit graph allows you to highlight different types of information in the swimlanes or changeset list:
For example, if you have the JIRA issues highlight active, clicking a changeset with a JIRA issue in the commit comment will show all other changesets with the same JIRA issue.
Before you begin:
To view the commit graph for a repository:
Selecting, or hovering on, a changeset (regardless of highlight) will display the following in the row for the changeset:
Choose Highlight > Lineage to show the ancestor and descendant changesets for a selected changeset.
Action | Behaviour |
---|---|
Click on a changeset in the changeset list | Highlights where a changeset comes from and where it propagates to, i.e. its ancestors and descendants. |
Hover over a changeset in a swimlane | Displays the changeset number and all the branches that the changeset is referenced in. This will include branches that you may not have swimlanes displayed for. |
Choose Highlight > JIRA issues to highlight all the changesets that have a JIRA issue key in the commit message.
This highlight type is only available if you have integrated FishEye with JIRA and linked your repository to a JIRA project.
Action | Behaviour |
---|---|
Click on a changeset in the changeset list | Highlights all other changesets that have the same JIRA issue key in the commit message. |
Hover over a changeset in a swimlane | Displays all branches that the changeset is referenced in, and all referenced JIRA issues. |
Choose Highlight > Reviewed changesets to highlight the changesets that have been reviewed (i.e. included in a Crucible review):
This highlight type is only available if you are using FishEye with Crucible.
Action | Behaviour |
---|---|
Click on a changeset in the changeset list | Highlights the changesets that are part of the same review as the selected changeset. |
Hover over a changeset in a swimlane | Displays all branches that the changeset is referenced in, and the Crucible review key. |
Choose Highlight > Author to highlight all the changesets submitted by a particular author.
Action | Behaviour |
---|---|
Click on a changeset in the changeset list | Highlights the changesets that were submitted by the same author. |
Hover over a changeset in a swimlane | Displays the changeset number and all the branches that the changeset is referenced in. |
Choose Highlight > Search to highlight all the changesets where the commit message contains the search term.
Action | Behaviour |
---|---|
Click on a changeset in the changeset list | Highlights the changesets that match the search term. |
Hover over a changeset in a swimlane | Displays the changeset number and all the branches that the changeset is referenced in. |
The 'All Branches' mode allows you to view commit activity across all branches of a repository. In this mode, the swimlane headers are not displayed. However, you can hover over any changeset to display information about the changeset, as described in the 'Highlighting Information in the Commit Graph' section above.
To see all the repository's branches in the commit graph:
Reordering swimlanes is useful if you just want to show branches in a certain order. However, ordering swimlanes is vital for Git repositories, as it is the only way to determine which branch a commit is from.
When you view the commit graph for a Git repository, FishEye works from the leftmost swimlane to the right and, for each swimlane, checks if the commit is in that branch:
For example, if the 'master' swimlane is to the left of another swimlane, e.g. 'fisheye-2.6' branch, there will be no changesets shown in the 'fisheye-2.6' swimlane, as all the commits will be picked up in the 'master' swimlane. However, if you move the 'fisheye-2.6' swimlane to the left of the 'master' swimlane, it will pick up all of the FishEye 2.6 commits.
For more information, read this Knowledge Base article: Ordering of Branches Important When Visualising Git Changeset