- 22 12月, 2016 1 次提交
-
-
由 Tiago Botelho 提交于
-
- 06 12月, 2016 1 次提交
-
-
由 Bob Van Landuyt 提交于
When a merge request can only be merged when all discussions are resolved. This feature allows to easily delegate those discussions to a new issue, while marking them as resolved in the merge request. The user is presented with a new issue, prepared with mentions of all unresolved discussions, including the first unresolved note of the discussion, time and link to the note. When the issue is created, the discussions in the merge request will get a system note directing the user to the newly created issue.
-
- 19 11月, 2016 1 次提交
-
-
由 Ruben Davila 提交于
-
- 18 11月, 2016 2 次提交
-
-
- 29 10月, 2016 1 次提交
-
-
由 Guilherme Salazar 提交于
fix issues pointed out in !6527 add task completion status feature to CHANGELOG
-
- 20 10月, 2016 5 次提交
-
-
- 07 10月, 2016 1 次提交
-
-
由 Stan Hu 提交于
The Sortable concern has a default scope that adds ORDER BY to all queries. EXPLAIN ANALYZE shows that this additional ORDER BY statement causes the SQL optimizer to use the wrong index, which leads to a load time of 2.9 s vs 0.073 ms just for the SELECT call. The minimal change here is to re-implement find_by using where and reorder to remove the ORDER BY clause in IssuesController#index. Closes #23075
-
- 27 9月, 2016 1 次提交
-
-
由 Paco Guzman 提交于
-
- 22 9月, 2016 1 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 20 9月, 2016 1 次提交
-
-
由 barthc 提交于
-
- 08 9月, 2016 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 01 9月, 2016 1 次提交
-
-
由 Felipe Artur 提交于
-
- 26 8月, 2016 1 次提交
-
- 22 8月, 2016 1 次提交
-
-
由 Valery Sizov 提交于
-
- 17 8月, 2016 1 次提交
-
-
由 Douwe Maan 提交于
-
- 16 8月, 2016 1 次提交
-
-
由 Patricio Cano 提交于
- Added controller actions as reusable concerns - Added controller tests
-
- 13 8月, 2016 1 次提交
-
-
由 Douwe Maan 提交于
-
- 02 8月, 2016 2 次提交
-
-
由 Robert Speicher 提交于
Now we link to the standard `IssuesController#new` action, and let it redirect if we're using an external tracker.
-
由 Robert Speicher 提交于
Prior, in order to display the correct link to "Issues" in the project navigation, we were performing a check against the project to see if it used an external issue tracker, and if so, we used that URL. This was inefficient. Now, we simply _always_ link to `namespace_project_issues_path`, and then in the controller we redirect to the external tracker if it's present. This also removes the need for the url_for_issue helper. Bonus!
🎉
-
- 01 8月, 2016 1 次提交
-
-
由 zs 提交于
Provide more sensible default sort order for issues and merge requests based on the following table: | type | state | default sort order | |----------------|--------|--------------------| | issues | open | last created | | issues | closed | last updated | | issues | all | last created | | merge requests | open | last created | | merge requests | merged | last updated | | merge requests | closed | last updated | | merge requests | all | last created |
-
- 27 7月, 2016 6 次提交
-
-
由 Patricio Cano 提交于
Refactor spam validation to a concern that can be easily reused and improve legibility in `SpamCheckService`
-
由 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.
-
由 Patricio Cano 提交于
-
由 Patricio Cano 提交于
-
由 Patricio Cano 提交于
-
- 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
-