- 27 7月, 2016 2 次提交
-
-
由 Stan Hu 提交于
-
由 Stan Hu 提交于
NotesHelper#note_editable? and ProjectTeam#human_max_access currently take about 16% of the load time of an issue page. This MR preloads the maximum access level of users for all notes in issues and merge requests with several queries instead of one per user and caches the result in RequestStore.
-
- 15 7月, 2016 1 次提交
-
-
由 Cairo Noleto 提交于
fixies #19747
-
- 14 7月, 2016 1 次提交
-
- 13 7月, 2016 1 次提交
-
-
由 Valery Sizov 提交于
-
- 02 7月, 2016 1 次提交
-
-
由 Grzegorz Bizon 提交于
-
- 25 6月, 2016 2 次提交
-
-
由 Felipe Artur 提交于
-
由 Felipe Artur 提交于
-
- 24 6月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
This commit changes the way certain documents are rendered (currently only Notes) and how documents are redacted. Previously both rendering and redacting would run on a per document basis. The result of this was that for every document we'd have to run countless queries just to figure out if we could display a set of links or not. This commit changes things around so that redacting Markdown documents is no longer tied into the html-pipeline Gem. This in turn allows it to redact multiple documents in a single pass, thus reducing the number of queries needed. In turn rendering issue/merge request notes has been adjusted to take advantage of this new setup. Instead of rendering Markdown somewhere deep down in a view the Markdown is rendered and redacted in the controller (taking the current user and all that into account). This has been done in such a way that the "markdown()" helper method can still be used on its own. This particular commit also paves the way for caching rendered HTML on object level. Right now there's an accessor method Note#note_html which is used for setting/getting the rendered HTML. Once we cache HTML on row level we can simply change this field to be a column and call a "save" whenever needed and we're pretty much done.
-
- 14 6月, 2016 2 次提交
-
-
由 Phil Hughes 提交于
-
由 Phil Hughes 提交于
Added a button into the sidebar for issues & merge requests to allow users to manually create todo items Closes #15045
-
- 04 6月, 2016 4 次提交
-
-
由 Alfredo Sumaran 提交于
-
由 Sean McGivern 提交于
-
由 Alfredo Sumaran 提交于
-
由 Alfredo Sumaran 提交于
-
- 06 5月, 2016 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
-
- 01 5月, 2016 1 次提交
-
-
由 Grzegorz Bizon 提交于
Closes #15533
-
- 29 4月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
This button depends on Issue#can_be_worked_on? which in turn depends on Issue#related_branches. By rendering this button asynchronously we can finally remove all usages of Issue#related_branches and Issue#referenced_merge_requests from the issues "show" page.
-
- 22 4月, 2016 1 次提交
-
-
由 Phil Hughes 提交于
Closes #15515
-
- 21 4月, 2016 3 次提交
-
-
由 Phil Hughes 提交于
-
由 Mehmet Beydogan 提交于
Add due_date text field to sidebar issue#show Add ability sorting issues by due date ASC and DESC Add ability to filtering issues by No Due Date, Any Due Date, Due to tomorrow, Due in this week options Add handling issue due_date field for MergeRequest Update CHANGELOG Fix ambigous match for issues#show sidebar Fix SCREAMING_SNAKE_CASE offenses for due date contants Add specs for due date sorting and filtering on issues
-
由 Phil Hughes 提交于
Created issuable singleton to house the filtering
-
- 19 4月, 2016 1 次提交
-
-
由 Phil Hughes 提交于
-
- 18 4月, 2016 1 次提交
-
-
由 Timothy Andrew 提交于
-
- 14 4月, 2016 1 次提交
-
-
由 Jacob Schatz 提交于
-
- 13 4月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
Currently this works by loading the HAML partials via XHR. While this is not the nicest setup it _is_ the easiest setup using the tools we currently have. Loading this data asynchronously doesn't make loading the related MRs/branches itself faster, it merely ensures that loading the issue itself is not slowed down. Fixes gitlab-org/gitlab-ce#14949
-
- 12 4月, 2016 1 次提交
-
-
由 Timothy Andrew 提交于
- Previously, the controller held the logic to calculate related branches, which was: `<branches ending with `issue.iid`> - <branches with a merge request referenced in the current issue>` - This logic belongs in the `related_branches` method, not in the controller. This commit makes this change. - This means that `Issue#related_branches` now needs to take a `User`. When we find the branches that have a merge request referenced in the current issue, this is limited to merge requests that the current user has access to. - This is not directly related to #14566, but is a related refactoring.
-
- 25 3月, 2016 8 次提交
-
-
由 Jacob Schatz 提交于
Add user avatar to user selection
-
由 Alfredo Sumaran 提交于
-
由 Jacob Schatz 提交于
-
由 Jacob Schatz 提交于
-
由 Jacob Schatz 提交于
-
由 Jacob Schatz 提交于
-
由 Jacob Schatz 提交于
-
由 Jacob Schatz 提交于
-
- 21 3月, 2016 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
-
- 20 3月, 2016 4 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 Robert Speicher 提交于
-
由 Zeger-Jan van de Weg 提交于
-
由 Zeger-Jan van de Weg 提交于
-