summaryrefslogtreecommitdiffstats
path: root/src/com
Commit message (Collapse)AuthorAgeFilesLines
...
* Include owned repositories while editing a user modelJames Moger2012-11-011-0/+10
|
* Ignore permission definitions for admins, it just confuses thingsJames Moger2012-11-014-30/+49
|
* Centralize Manager row height settingJames Moger2012-11-0111-14/+1
|
* Gracefully deal with missing repository in permissions ui (issue 155)James Moger2012-11-0110-37/+61
|
* Renamed isEditable to mutableJames Moger2012-10-319-20/+20
|
* Improve transparency of permissions by indicating permission sourceJames Moger2012-10-3111-133/+213
|
* Personal repositories must always be owned by the account the repo is stored inJames Moger2012-10-311-1/+1
|
* Teams must be sortedJames Moger2012-10-312-1/+3
|
* Repository cache must be case-insensitive to match permissionsJames Moger2012-10-311-9/+9
|
* Don't even bother running Lucene indexer if we are GCing anythingJames Moger2012-10-313-0/+23
|
* Fixed ticgit ticket urls (issue 157)James Moger2012-10-311-1/+1
|
* Include gravatar images in registrant permissions panel, if configuredJames Moger2012-10-313-8/+40
|
* Clarified delete permission choiceJames Moger2012-10-311-1/+1
|
* Reject add if permission selector has not been setJames Moger2012-10-311-0/+3
|
* Enable verify committer iff >= push restrictedJames Moger2012-10-312-9/+16
|
* Handle case of missing repository in Manager (issue 155)James Moger2012-10-311-1/+9
|
* Fixed intermittent incomplete fork networkJames Moger2012-10-301-0/+10
|
* Replaced fork iconJames Moger2012-10-301-2/+2
|
* Added null checkinng and logging for edit user permissions (issue 155)James Moger2012-10-301-3/+10
|
* Fix intermittent Wicket page expirations on EditNNN pagesJames Moger2012-10-304-0/+33
|
* Moved owner field onto access permissions tabJames Moger2012-10-302-13/+21
|
* Refactor GC period into an integer for simpler translationsJames Moger2012-10-305-9/+67
| | | | Also hooked-up GC settings in the Manager.
* Fixed missing repo counts on user projectsJames Moger2012-10-301-3/+4
|
* Stabilizing and polishing permissions ui. Still in-progress.James Moger2012-10-2921-112/+510
|
* Use repository swatch coloring in registrant permissions panelJames Moger2012-10-292-2/+13
|
* Experimental JGit-based GC ExecutorJames Moger2012-10-2816-40/+442
|
* Do not display link for add team in LDAP-managed teams setup (issue 153)James Moger2012-10-281-1/+1
|
* Fixed missing project counts in project headersJames Moger2012-10-242-2/+2
|
* Implemented exclusion (X) permissionJames Moger2012-10-233-3/+7
|
* Enforce strict order for permission determinationJames Moger2012-10-232-12/+18
| | | | | | | | | | | | | | | The order of permissions defined within a user or team is preserved during read and write. This order is important for determining the regex match used within the user or team object. If the user is an admin or repository owner, then RW+ Else if user has an explicit permission, use that Else check for the first regex match in user permissions Else check for the HIGHEST permission from team memberships If the team is an admin team, then RW+ Else if a team has an explicit permission, use that Else check for the first regex match in team permissions
* Add some common regex filters to the repository listsJames Moger2012-10-235-29/+80
|
* Repository sorting should be case-insensitiveJames Moger2012-10-231-0/+2
|
* Tweak permissions panel layout a bitJames Moger2012-10-221-2/+2
|
* Fixed bug where owner could not edit a repository through web uiJames Moger2012-10-221-3/+4
|
* Permission regexes are now case-insensitiveJames Moger2012-10-223-4/+18
|
* Fixed null pointer exceptions Manager create User and TeamJames Moger2012-10-222-4/+14
|
* Differentiate between an explicit permission and a regex permissionJames Moger2012-10-2210-27/+126
|
* Renamed method to UserModel.canCreate(String repository)James Moger2012-10-222-4/+3
|
* Ensure illegal repository names are rejected in create-on-pushJames Moger2012-10-221-4/+22
|
* Implemented optional create-on-pushJames Moger2012-10-215-6/+142
| | | | | | | | | | | | | | | | If this feature is enabled then permitted users can automatically create a repository when pushing to one that does not yet exist. Permitted users are administrators and any user with the CREATE role. If the pushing account is an administrator, the created repository may be located in any folder/project space. This reposiory will inherit the server's default access restriction and authorization control. The repository owner will be the pushing account. If the pushing account is a regular user with the CREATE role, the repository can only be located in the account's personal folder (~username/myrepo.git). This repository will be VIEW restricted and accessible by NAMED users. The repository owner will be the pushing account.
* Switch to tab interface for Edit User and Edit Team for consistencyJames Moger2012-10-203-27/+87
|
* Split edit repository page into tabsJames Moger2012-10-191-33/+81
|
* Construct access permissions from already retrieved dataJames Moger2012-10-192-12/+21
|
* Split committer verification description into two stringsJames Moger2012-10-192-2/+3
|
* Completed permissions UI, RPC, and Manager support (issue 36)James Moger2012-10-1933-653/+540
|
* New permissions UI for EditRepository (issue 36)James Moger2012-10-199-38/+552
|
* Exclude submodules from zip downloads (issue 151)James Moger2012-10-191-0/+3
|
* New permissions UI for EditUser and EditTeam (issue 36)James Moger2012-10-1912-32/+339
|
* Added UserModel null checkJames Moger2012-10-191-4/+6
|
* Allows integration of GitBlit as plug-in in other projects.Luca Milanesio2012-10-205-28/+91
| | | | | | | | | | | | | | | There are now three new targets on the ANT build: - buildJAR: creates a GitBlit JAR including the GitBlit biz logic - installMaven: install GitBlit JAR as Maven module - uploadMaven: uploads GitBlit JAR to a Maven repository Additional extensions have been made to allow: a) GitBlit to load his resources outside of Wicket domain b) GitBlit to use an injected UserService c) Generic authentication of HTTP Request using 3rd party logic d) Load settings programmatically from an InputStream e) Use cookie authentication OR generic HTTP Request authentication for Wicket pages f) UserModel with branch-level security logic