| | |
|---|
| | | ### TODO (medium priority)
|
|---|
| | |
|
|---|
| | | * Gitblit: editable settings page in GO/WAR
|
|---|
| | | * Gitblit: tag repositories and offer views of repositories by tag (issue 27)
|
|---|
| | | * Gitblit: investigate create-repository-on-push.
|
|---|
| | | * Maybe a new user role to allow this?
|
|---|
| | | * Maybe a server setting to disable this completely?
|
|---|
| | |
|---|
| | | * push-restricted repositories would have anonymous R git:// access
|
|---|
| | | * clone-restricted repositories would prohibit git:// access
|
|---|
| | | * view-restricted repositories would prohibit git:// access
|
|---|
| | | * Gitblit: Consider using Git-style config file instead of Java properties file for user storage (users.config vs. users.properties)
|
|---|
| | | * this would allow for additional fields per user without bringing in a database
|
|---|
| | |
|
|---|
| | | ### TODO (low priority)
|
|---|
| | |
|
|---|
| | |
|---|
| | |
|
|---|
| | | ### IDEAS
|
|---|
| | |
|
|---|
| | | * Gitblit: implement branch permission controls as Groovy pre-receive script. |
|---|
| | | *Maintain permissions text file similar to a gitolite configuration file or svn authz file.*
|
|---|
| | | * Gitblit: consider user-subscribed email notifications for a repository branch as a built-in feature. |
|---|
| | | *There is a sample Groovy post-receive hook script which can send emails.*
|
|---|
| | | * Gitblit: aggregate RSS feeds by tag or subfolder
|
|---|
| | | * Gitblit: Consider creating more Git model objects and exposing them via the JSON RPC interface to allow inspection/retrieval of Git commits, Git trees, etc from Gitblit.
|
|---|
| | | * Gitblit: Stronger ticgit integration (issue 8)
|
|---|
