diff options
| author | James Moger <james.moger@gitblit.com> | 2012-10-05 17:44:53 -0400 |
|---|---|---|
| committer | James Moger <james.moger@gitblit.com> | 2012-10-05 17:44:53 -0400 |
| commit | 6662e38a4e252b6ed455ca8f11729d0f1440a3b0 (patch) | |
| tree | a16c60eebaac88d07248431dd96bda835314d04a /docs | |
| parent | dd79f46d8e39b041fcdc349d18f76dfbc038667e (diff) | |
| download | gitblit-6662e38a4e252b6ed455ca8f11729d0f1440a3b0.tar.gz gitblit-6662e38a4e252b6ed455ca8f11729d0f1440a3b0.zip | |
Implemented New Repository for personal repositories
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/04_releases.mkd | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/04_releases.mkd b/docs/04_releases.mkd index 55bdfd71..33362343 100644 --- a/docs/04_releases.mkd +++ b/docs/04_releases.mkd @@ -20,10 +20,10 @@ If you are updating from an earlier release AND you have indexed branches with t #### additions
- Added simple project pages. A project is a subfolder off the *git.repositoriesFolder*.
-- Added support for personal repositories. This builds on the simple project pages.
-Personal repositories are stored in *git.repositoriesFolder*/*~username*. Each user with personal repositories will have a user page, something like the GitHub profile page. Personal repositories have all the same features as common repositories.
+- Added support for personal repositories.
+Personal repositories can be created by accounts with the *create* permission and are stored in *git.repositoriesFolder/~username*. Each user with personal repositories will have a user page, something like the GitHub profile page. Personal repositories have all the same features as common repositories, except personal repositories can be renamed by their owner.
- Added support for server-side forking of a repository to a personal repository (issue 137)
-In order to fork a repository to a personal clone, the user account must have the *fork* permission **and** the repository must *allow forks*. The clone inherits the access restrictions of its origin. i.e. if Team A has access to the origin repository, then by default Team A also has access to the fork. This is to facilitate collaboration. However, the fork owner may change access to the fork and add/remove users/teams, etc as required.
+In order to fork a repository, the user account must have the *fork* permission **and** the repository must *allow forks*. The clone inherits the access restrictions of its origin. i.e. if Team A has access to the origin repository, then by default Team A also has access to the fork. This is to facilitate collaboration. The fork owner may change access to the fork and add/remove users/teams, etc as required __however__ it should be noted that all personal forks will be enumerated in the fork network regardless of access view restrictions. If you really must have an invisible fork, the clone it locally, create a new repository for your invisible fork, and push it back.
- Added support for X-Forwarded-Context for Apache subdomain proxy configurations (issue 135)
- Delete branch feature (issue 121, Github/ajermakovics)
- Added line links to blob view at the expense of zebra striping (issue 130)
|