- 14 6月, 2016 1 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 13 6月, 2016 6 次提交
-
-
由 Yorick Peterse 提交于
-
由 Yorick Peterse 提交于
Instead of updating a fixed number of rows (based on the amount of rows available at the start of the update) the method "update_column_in_batches" will now continue updating rows until it runs out of rows to process. For a table with a high rate of inserts this may result in the migration taking quite some time. However, the alternative is not all rows being updated or the "change_column_null" method raising an error due to there being NULL values.
-
由 Yorick Peterse 提交于
This ensures that whenever changing the NULL constraint of a column fails we still drop the column.
-
由 Gabriel Mazetto 提交于
-
由 Gabriel Mazetto 提交于
-
由 Gabriel Mazetto 提交于
-
- 12 6月, 2016 1 次提交
-
-
由 Stan Hu 提交于
Closes #18484
-
- 11 6月, 2016 2 次提交
-
-
由 Kamil Trzcinski 提交于
-
由 Stan Hu 提交于
Closes #12710
-
- 10 6月, 2016 6 次提交
-
-
由 Jacob Vosmaer 提交于
Auth.find was a very generic name for a very specific method. Auth.find_in_gitlab_or_ldap was inaccurate in GitLab EE where it also looks in Kerberos.
-
由 Rémy Coutable 提交于
Based on the feedback from reviewers. Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Rui Anderson 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Kamil Trzcinski 提交于
-
由 Douwe Maan 提交于
-
由 Stan Hu 提交于
!4318 broke the gitlab:db:drop_tables functionality for PostgreSQL. Closes #15259
-
- 09 6月, 2016 8 次提交
-
-
由 Kamil Trzcinski 提交于
-
-
由 Timothy Andrew 提交于
Original Comments ================= - Linking behaves as per rules documented here: https://gitlab.com/gitlab-org/gitlab-ce/blob/16568-document-wiki-linking-behavior/doc/markdown/wiki.md - All links (to other wiki pages) are rewritten to be at the level of the app root. We can't use links relative to the current page ('./foo', 'foo', '../foo'), because they won't work in the markdown preview, where the current page is suffixed with `/edit` - Move existing `WikiLinkFilter` specs to `WikiPipeline` spec. It makes sense to run these tests on the combined output of the pipeline, rather than a single filter, since we can catch issues with conflicting filters. - Add more tests to cover the new linking @rymai's Review =============== - Classes nested under `WikiLinkFilter` should declare `WikiLinkFilter`'s inherit, so nothing changes if the nested class is loaded first. - Add a blank line after a guard clause - Use keyword arguments for the `Rewriter` constructor - Invert a condition - use `if` instead of `unless` - Inline a `let` in `WikiPipeline` spec - it was only used in a single place - Change out of date spec names - Add a comment for every rewrite rule in `Rewriter`
-
由 Fatih Acet 提交于
-
由 Patricio Cano 提交于
-
由 Sean McGivern 提交于
Add a new application setting, after_sign_up_text. This is text to be rendered as Markdown and shown on the 'almost there' page after a user signs up, but before they've confirmed their account. Tweak the styles for that page so that centered lists look reasonable.
-
由 Alfredo Sumaran 提交于
-
由 Alfredo Sumaran 提交于
-
- 08 6月, 2016 3 次提交
-
-
由 Kamil Trzcinski 提交于
-
由 Alejandro Rodríguez 提交于
This was not a clear cut n+1 query, given that if you're directly subscribed to all issues that the API is returning you never really need to check for the notes. However, if you're subscribed to _all_ of them, then for each issuable you need to go once to `notes`, and once to `users` (for the authors). By preemtively loading notes and authors, at worst you have 1 extra query, and at best you saved 2n extra queries. We also took advantage of this preloading of notes when counting user notes.
-
由 Patricio Cano 提交于
-
- 07 6月, 2016 8 次提交
-
-
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
This is a temporary refactoring stub, that is planned to be removed after removing legacy config processor.
-
由 Patricio Cano 提交于
-
由 Connor Shea 提交于
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Felipe Artur 提交于
-
- 06 6月, 2016 5 次提交
-
-
由 Jacob Vosmaer 提交于
-
Fix comments on diff after LegacyDiffNote was extracted from Note
-
While Octokit auto pagination set the page size to the maximum 100, and seek to not overstep the rate limit. When the rate limit is reached its raises an exception, and stop doing new requests. Here we use a custom pattern for traversing large lists, so we can check if we’ll reach the rate limit and wait the API to reset the rate limit before making new requests.
-
-
由 Douwe Maan 提交于
-