Preliminary implementation of server-side forking (issue 137)

The fork mechanism clones the repository , access restrictions, and
other config options.  The app has been updated throughout to handle
personal repositories and to properly display origin/fork links.

In order to fork a repository the user account must have the #fork role,
the origin repository must permit forking, and the user account must
have standard clone permissions to the repository.

Because forking introduces a new user role no existing user accounts can
automatically begin forking a repository.  This is both a pro and a con.

Since the fork has the same access restrictions as the origin repository,
those who can access the origin may also access the fork.  This is intentional
to facilitate integration-manager workflow.  The fork owner does have the
power to completely change the access restrictions of his/her fork.

1 files changed, 1 insertions, 1 deletions

diff --git a/src/com/gitblit/utils/ActivityUtils.java b/src/com/gitblit/utils/ActivityUtils.java
index 02a9924b..e5159942 100644
--- a/src/com/gitblit/utils/ActivityUtils.java
+++ b/src/com/gitblit/utils/ActivityUtils.java
@@ -94,7 +94,7 @@ public class ActivityUtils {
 					branches.add(objectId);

 				}

 				Map<ObjectId, List<RefModel>> allRefs = JGitUtils

-						.getAllRefs(repository);

+						.getAllRefs(repository, model.showRemoteBranches);

 

 				for (String branch : branches) {

 					String shortName = branch;