| | |
|---|
| | | 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, the user account must have the *fork* permission **and** the repository must *allow forks*. The clone inherits the access list of its origin. i.e. if Team A has clone access to the origin repository, then by default Team A also has clone 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 <u>however</u> 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 to Gitblit.
|
|---|
| | | - Added optional *create-on-push* support |
|---|
| | | **New:** *git.allowCreateOnPush=true*
|
|---|
| | | - Added simple project pages. A project is a subfolder off the *git.repositoriesFolder*.
|
|---|
| | | - Added support for X-Forwarded-Context for Apache subdomain proxy configurations (issue 135)
|
|---|
| | | - Delete branch feature (issue 121, Github/ajermakovics)
|
|---|
