summaryrefslogtreecommitdiffstats
path: root/src/main/java/com/gitblit/models
Commit message (Collapse)AuthorAgeFilesLines
* Git-LFS supportPaul Martin2015-10-101-0/+159
| | | | | | | | | | | | | | + Metadata maintained in append-only JSON file providing complete audit history. + Filestore menu item + Lists filestore items + Current size and availability + Link to GitBlit Filestore help page (top right) + Hooks into existing repository permissions + Uses default repository path for out-of-box operation with Git-LFS client + accessRestrictionFilter now has access to http method and auth header + Testing for servlet and manager
* Simplify RefModel datesJames Moger2015-09-181-6/+1
|
* Use author date to be consistent with other tools (fixes #919)James Moger2015-09-181-3/+3
|
* allow advertising gitblit privileges for external URLsJoel Johnson2015-07-011-2/+2
| | | | | | | | | | | | | | | | commit c20191fc0931a19bec0df1ab2b56f287e5d8b7c7 enabled support for hiding internal URLs, but didn't consider that it broke the evaluation of permissions (used for tickets, etc.), and caused a NPE on repoUrl.permission when trying to view the TicketPage. With all internal mechanisms disabled, it would result in the first URL being external with unknown permissions. This adds an option to use internal permissions even for external URLs. Note that this does not grant any additional permissions, but does offer the option to have gitblit advertise the full set of what is allowed, even if the external URL imposes additional restrictions.
* Tickets - Priority, Severity optionsPaul Martin2014-10-201-1/+119
| | | | | | | | | + Severity indicated via new character indicator and color of ticket icon on ticket list + Priority indicated via new priority icon and color on ticket list + Indexed as integers to provide sorting and maintain language neutral index + Colours and indicator text controlled through CSS classes priority-<x> & severity-<x> + UITicketTest created to generate tickets of all types to ease debugging
* New Ticket Type - MaintenancePaul Martin2014-10-191-2/+2
| | | | | | | + Indended for identifiying and loggin maintenance of development tools and systems to provide an integrated means to satisfy ISO requirements + Improved alignment of query icons via fixed width attribute
* Add NO CHANGE REQUIRED ticket statusJames Moger2014-09-171-4/+4
|
* Ensure TicketModel comment text is not null in hasComment() testJames Moger2014-09-171-1/+1
|
* Fix ticket mail dropping bug when author does not have an addressJames Moger2014-09-081-1/+1
|
* Add clone transport user preferenceJames Moger2014-06-051-0/+11
|
* Add "email me on my ticket changes" preferenceJames Moger2014-06-051-0/+13
|
* Revise language/locale preference handlingJames Moger2014-06-051-1/+5
|
* Allow plugins to extend the top navbar and repository navbarJames Moger2014-05-051-0/+140
| | | | | This change also ties the plugin manager into the Wicket framework and allows plugins to contribute and mount new pages which are linked by the top navbar and repository navbar extensions.
* Overhaul menu item classes and add AdminMenuExtension pointJames Moger2014-05-051-0/+302
|
* Fix inconsistency with owner permissions checkJames Moger2014-05-012-5/+5
|
* Fix bug introduced in 67278f5James Moger2014-04-281-1/+1
|
* Fix forcing default locale to en or LANG_CC for web uiJames Moger2014-04-281-0/+6
|
* Simplify current plugin release detection, ignore currentRelease registry fieldJames Moger2014-04-231-33/+14
|
* Filter the current plugin release by the system versionJames Moger2014-04-171-4/+28
|
* Removed obsolete Gravatar profile codeJames Moger2014-04-151-83/+0
|
* Update to pf4j 0.8.0James Moger2014-04-151-4/+4
|
* Upgrade plugin commandJames Moger2014-04-131-2/+2
|
* Eliminate plugin name, stick with id and descriptionJames Moger2014-04-121-5/+2
|
* Improve plugin manager based on upstreamed contributions to pf4jJames Moger2014-04-101-2/+19
|
* Allow specifying accepted PUSH transportsJames Moger2014-04-101-0/+3
|
* Implement simple JSON-based plugin registry and install commandJames Moger2014-04-101-0/+143
|
* Implement management commands in repositories dispatcherJames Moger2014-04-101-1/+11
|
* Add review SSH commandDavid Ostrovsky2014-04-101-1/+12
| | | | Change-Id: Ia03c15608814346522c548ff2439ee672ccb0d28
* Fix intermittent NPE in getting commit date in RefModelJames Moger2014-04-081-3/+12
|
* Implement setting removal for configuration settingsJames Moger2014-03-271-0/+4
|
* Fix TicketModel modList bug when a field was set multiple timesJames Moger2014-03-121-1/+15
|
* Add closed status for milestones and abandoned status for ticketsJames Moger2014-03-111-4/+6
|
* Allow configuring the default integration branch for a repositoryJames Moger2014-03-081-0/+1
|
* Allow selection of integration branch in new ticket pageJames Moger2014-03-081-3/+9
|
* Allow resolve for proposal workflowsJames Moger2014-03-061-1/+1
|
* Centralized ticket editing permission controlsJames Moger2014-03-051-3/+14
|
* Implement user "disabled" flag as an alternative to deleting the accountJames Moger2014-03-041-0/+1
|
* Ticket tracker with patchset contributionsJames Moger2014-03-033-0/+1309
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A basic issue tracker styled as a hybrid of GitHub and BitBucket issues. You may attach commits to an existing ticket or you can push a single commit to create a *proposal* ticket. Tickets keep track of patchsets (one or more commits) and allow patchset rewriting (rebase, amend, squash) by detecing the non-fast-forward update and assigning a new patchset number to the new commits. Ticket tracker -------------- The ticket tracker stores tickets as an append-only journal of changes. The journals are deserialized and a ticket is built by applying the journal entries. Tickets are indexed using Apache Lucene and all queries and searches are executed against this Lucene index. There is one trade-off to this persistence design: user attributions are non-relational. What does that mean? Each journal entry stores the username of the author. If the username changes in the user service, the journal entry will not reflect that change because the values are hard-coded. Here are a few reasons/justifications for this design choice: 1. commit identifications (author, committer, tagger) are non-relational 2. maintains the KISS principle 3. your favorite text editor can still be your administration tool Persistence Choices ------------------- **FileTicketService**: stores journals on the filesystem **BranchTicketService**: stores journals on an orphan branch **RedisTicketService**: stores journals in a Redis key-value datastore It should be relatively straight-forward to develop other backends (MongoDB, etc) as long as the journal design is preserved. Pushing Commits --------------- Each push to a ticket is identified as a patchset revision. A patchset revision may add commits to the patchset (fast-forward) OR a patchset revision may rewrite history (rebase, squash, rebase+squash, or amend). Patchset authors should not be afraid to polish, revise, and rewrite their code before merging into the proposed branch. Gitblit will create one ref for each patchset. These refs are updated for fast-forward pushes or created for rewrites. They are formatted as `refs/tickets/{shard}/{id}/{patchset}`. The *shard* is the last two digits of the id. If the id < 10, prefix a 0. The *shard* is always two digits long. The shard's purpose is to ensure Gitblit doesn't exceed any filesystem directory limits for file creation. **Creating a Proposal Ticket** You may create a new change proposal ticket just by pushing a **single commit** to `refs/for/{branch}` where branch is the proposed integration branch OR `refs/for/new` or `refs/for/default` which both will use the default repository branch. git push origin HEAD:refs/for/new **Updating a Patchset** The safe way to update an existing patchset is to push to the patchset ref. git push origin HEAD:refs/heads/ticket/{id} This ensures you do not accidentally create a new patchset in the event that the patchset was updated after you last pulled. The not-so-safe way to update an existing patchset is to push using the magic ref. git push origin HEAD:refs/for/{id} This push ref will update an exisitng patchset OR create a new patchset if the update is non-fast-forward. **Rebasing, Squashing, Amending** Gitblit makes rebasing, squashing, and amending patchsets easy. Normally, pushing a non-fast-forward update would require rewind (RW+) repository permissions. Gitblit provides a magic ref which will allow ticket participants to rewrite a ticket patchset as long as the ticket is open. git push origin HEAD:refs/for/{id} Pushing changes to this ref allows the patchset authors to rebase, squash, or amend the patchset commits without requiring client-side use of the *--force* flag on push AND without requiring RW+ permission to the repository. Since each patchset is tracked with a ref it is easy to recover from accidental non-fast-forward updates. Features -------- - Ticket tracker with status changes and responsible assignments - Patchset revision scoring mechanism - Update/Rewrite patchset handling - Close-on-push detection - Server-side Merge button for simple merges - Comments with Markdown syntax support - Rich mail notifications - Voting - Mentions - Watch lists - Querying - Searches - Partial miletones support - Multiple backend options
* Improve notification api by introducing the Mailing modelJames Moger2014-02-281-0/+111
|
* Show "Displayname (username)" in palettes for edit team and repository pagesAlfred Schmid2014-02-191-0/+112
|
* Remove deprecated methods from User and Team modelsJames Moger2013-12-112-89/+0
| | | | Change-Id: Ief3231270e55b8e4075de45c70ee24517b05b3fc
* Fix NPE on usermodel account type checkingJames Moger2013-12-111-1/+3
| | | | Change-Id: I964381a896e8c8bf8cce5f19a83fd7c33ef5c9bd
* Fix external authentication failureJames Moger2013-12-111-1/+2
| | | | Change-Id: I0f415941a4bfd5e63d85c60613cea0c7d10cbb49
* Revised committer verification to require email addressJames Moger2013-11-291-8/+5
| | | | Change-Id: I5298c93e03099813f5713a4effd87913429aa3dc
* Refactor user services and separate authentication (issue-281)James Moger2013-11-292-8/+7
| | | | Change-Id: I336e005e02623fc5e11a4f8b4408bea5465a43fd
* Extract RuntimeManager from GitBlit singletonJames Moger2013-11-291-4/+3
| | | | Change-Id: I5358389396f816da979ec18a31421c2d2b67b3d9
* Eliminate the "enumerate documentation" repository settingJames Moger2013-11-141-2/+0
| | | | Change-Id: I3a7c13b4c626f8b5ea2a63717dfe4249c19eebb4
* Implement mirror executor (issue-5)James Moger2013-11-133-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | The mirror executor will fetch ref updates for repository mirrors. This feature is disabled by default and can be enabled by setting git.enableMirroring=true. The period between update checks is configurable, but it is global. An individual rpeository may not set it's own update schedule. Requirements: 1. you must manually clone the repository using native git git clone --mirror git://somewhere.com/myrepo.git 2. the "origin" remote must be the mirror source 3. the "origin" repository must be accessible without authentication OR the credentials must be embedded in the origin url (not recommended) Notes: 1. "origin" SSH urls are untested and not likely to work 2. mirrors cloned while Gitblit is running are likely to require clearing the gitblit cache (link on the repositories page of an administrator account) 3. Gitblit will automatically repair any invalid fetch refspecs with a "//" sequence. Change-Id: I4bbe3fb2df106366ae4c2313596d0fab0dfcac46
* Remove "show readme" flag in favor of automatic detectionJames Moger2013-10-251-2/+0
| | | | | | | Automatic detection also will now also display a plain text "readme" or "readme.txt" file. Change-Id: Id6be729bdc469e7a5cfd1f4144df340a6b93475e
* Remove remaining TicGit tickets referencesJames Moger2013-09-301-2/+0
| | | | Change-Id: I431659cf1d57a8d9bffb065fa47e1296e7f8c838
generated by cgit v1.2.3 (git 2.39.1) at 2025-05-06 12:33:21 +0000