summaryrefslogtreecommitdiffstats
path: root/src/com/gitblit/models
Commit message (Collapse)AuthorAgeFilesLines
* Show indicators for Sparkleshared repositoriesJames Moger2013-01-111-0/+6
|
* Improve pushlog api and model classJames Moger2013-01-062-5/+55
|
* Draft mechanism to record a push log as a hidden orphan branchJames Moger2013-01-053-83/+270
|
* Support local accounts with LdapUserService and RedmineUserService (issue-183)James Moger2013-01-041-0/+8
|
* Cache and re-use project markdown content (issue-172)James Moger2013-01-031-0/+2
|
* Harden metrics from polluted data (issue-176)James Moger2012-12-071-2/+2
|
* Fixed anonymous browsing of branch panelJames Moger2012-12-061-0/+7
|
* Global and per-repository setting to throttle prolific repos in Activity ↵James Moger2012-12-051-0/+1
| | | | page (issue-173)
* Support symlink display in tree and commit pages (issue-171)James Moger2012-12-031-0/+4
|
* Fixed branch view regression (issue-175)James Moger2012-12-031-1/+1
|
* Command-line tool to generate client certificate bundles for existing usersJames Moger2012-11-231-0/+5
|
* Permission filtering in web uiJames Moger2012-11-022-3/+73
| | | | | Present the mutable permissions by default. Allow the administrator or owner to toggle the displayed permissions to see how the user and team permissions are applied to a repository.
* Ignore permission definitions for admins, it just confuses thingsJames Moger2012-11-012-7/+14
|
* Gracefully deal with missing repository in permissions ui (issue 155)James Moger2012-11-012-4/+4
|
* Renamed isEditable to mutableJames Moger2012-10-313-8/+8
|
* Improve transparency of permissions by indicating permission sourceJames Moger2012-10-313-31/+122
|
* Teams must be sortedJames Moger2012-10-311-1/+2
|
* Refactor GC period into an integer for simpler translationsJames Moger2012-10-301-1/+1
| | | | Also hooked-up GC settings in the Manager.
* Stabilizing and polishing permissions ui. Still in-progress.James Moger2012-10-293-10/+54
|
* Experimental JGit-based GC ExecutorJames Moger2012-10-281-0/+5
|
* 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
* Permission regexes are now case-insensitiveJames Moger2012-10-222-4/+5
|
* Differentiate between an explicit permission and a regex permissionJames Moger2012-10-223-3/+30
|
* Renamed method to UserModel.canCreate(String repository)James Moger2012-10-221-3/+2
|
* Implemented optional create-on-pushJames Moger2012-10-211-0/+22
| | | | | | | | | | | | | | | | 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.
* Completed permissions UI, RPC, and Manager support (issue 36)James Moger2012-10-195-119/+27
|
* New permissions UI for EditRepository (issue 36)James Moger2012-10-192-0/+102
|
* New permissions UI for EditUser and EditTeam (issue 36)James Moger2012-10-193-0/+86
|
* Allows integration of GitBlit as plug-in in other projects.Luca Milanesio2012-10-201-1/+6
| | | | | | | | | | | | | | | 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
* Experimental committer verificationJames Moger2012-10-112-0/+29
|
* Support Team canAdmin, canCreate, and canFork (issue 36)James Moger2012-10-102-7/+71
|
* Add regex permission matching to hasRepositoryPermission check (issue 36)James Moger2012-10-102-2/+30
|
* Try regex permission matching if exact permission is not found (issue 36)James Moger2012-10-102-0/+22
|
* Finer-grained repository access permissions (issue 36)James Moger2012-10-103-40/+279
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Implemented discrete repository access permissions to replace the really primitive course-grained permissions used to this point. This implementation allows for finer-grained access control, but still falls short of integrated, branch-based permissions sought by some. Access permissions follow the conventions established by Gitosis and Gitolite so they should feel immediately comfortable to experienced users. This permissions infrastructure is complete and works exactly as expected. Unfortunately, there is no ui in this commit to change permissions, that will be forthcoming. In the meantime, Gitblit hot-reloads users.conf so the permissions can be manipulated at runtime with a text editor. The following per-repository permissions are now supported: - V (view in web ui, RSS feeds, download zip) - R (clone) - RW (clone and push) - RWC (clone and push with ref creation) - RWD (clone and push with ref creation, deletion) - RW+ (clone and push with ref creation, deletion, rewind) And a users.conf entry looks something like this: [user "hannibal"] password = bossman repository = RWD:topsecret.git
* Implemented New Repository for personal repositoriesJames Moger2012-10-051-0/+18
|
* Fix anonymous browsing of user profile pageJames Moger2012-10-032-1/+5
|
* Use anonymous usermodel in a few placesJames Moger2012-10-031-4/+4
|
* Fix fork detection on WindowsJames Moger2012-10-031-0/+4
|
* Display entire fork network. Link as appropriate for user permissions.James Moger2012-10-033-8/+29
|
* Moved the fork mechanism from a javascript link to a separate pageJames Moger2012-10-021-0/+3
|
* Method to generate fork network graphJames Moger2012-10-011-0/+80
|
* Show fork links according to user permissions. Improve fork detection.James Moger2012-10-011-0/+10
|
* Preliminary implementation of server-side forking (issue 137)James Moger2012-09-293-0/+82
| | | | | | | | | | | | | | | | | | 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.
* Revised delete branch feature (issue 121)James Moger2012-09-201-0/+3
|
* Draft project pages, project metadata, and RSS feedsJames Moger2012-09-071-0/+95
| | | | | | This is an in-progress feature to offer an interface for grouped repositories. This may help installations with large numbers of repositories stay organized. It also will be part of a future, more advanced security model.
* Submodules supportJames Moger2012-08-102-4/+53
|
* Improve submodule checking in LuceneExecutor (issue-119)James Moger2012-08-101-0/+11
|
* Per-repository authorization control: AUTHENTICATED and NAMED (issue 117)James Moger2012-08-022-1/+11
|
* Forgot to commit UserModel with cookie fieldJames Moger2012-07-111-0/+1
|
* Revised TimeUtils for localizationJames Moger2012-06-151-2/+2
| | | | | | | | TimeUtils needs to output localized strings like "5 days ago" and "6 months". In order to do this it needs a translation resource. Additionally, that resource can not be static because the single Gitblit server can handle multiple connections in different locales/languages. TimeUtils has changed from a collection of static methods to some static methods and some instance methods. A TimeUtils is instantiated with an optional resource bundle which contains the preferred translation. If the resourec bundle is null or the requested translation key does not exist, an English default will be used. This change required adjusting the signatures of several key methods and that cascaded out to adjusting those methods calls in many, many classes.
generated by cgit v1.2.3 (git 2.39.1) at 2025-02-20 02:08:14 +0000