- 27 7月, 2016 2 次提交
-
-
由 Patricio Cano 提交于
-
由 Patricio Cano 提交于
-
- 26 7月, 2016 6 次提交
-
-
由 Sean McGivern 提交于
We can't reuse the existing value of the format parameter, because on the merge request page that's 'json', so the link would go to a JSON file. We can't set it to HTML, because that adds '.html' the URL, which breaks the compare view (and looks bad). Setting it to nil uses the default format, which in all of these cases is HTML anyway.
-
由 Katarzyna Kobierska 提交于
-
由 Paco Guzman 提交于
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Clement Ho 提交于
-
- 25 7月, 2016 5 次提交
-
-
由 Stan Hu 提交于
We have a number of bugs caused by cache keys not being flushed properly during deletion of a project. Add the project ID to ensure this never happens. Closes #20027
-
由 Timothy Andrew 提交于
1. So we can build the markdown preview URL for it. 2. We can't skip the slug in this case, because the slug is used to construct relative markdown URLs. 3. Add rspec feature tests to cover creating wiki pages with spaces/hyphens in the name. 4. Add rspec feature tests for markdown preview URL rewriting, which was only covered by unit tests up to this point.
-
由 Fatih Acet 提交于
-
由 winniehell 提交于
-
由 Alejandro Rodríguez 提交于
This reverts merge request !5375
-
- 24 7月, 2016 4 次提交
-
-
由 Stan Hu 提交于
Closes gitlab-com/support-forum#874
-
由 winniehell 提交于
-
由 Scott Le 提交于
-
由 Douwe Maan 提交于
Fix bug where replies to commit notes displayed in the MR discussion tab wouldn't show up on the commit page
-
- 23 7月, 2016 6 次提交
-
-
由 Stan Hu 提交于
Helping to diagnose #20178
-
由 Katarzyna Kobierska 提交于
Test for showing GitLab Workhorse version on Admin Dashboard Refactoring
-
由 winniehell 提交于
-
由 Ahmad Sherif 提交于
-
由 barthc 提交于
-
由 Annabel Dunstone 提交于
-
- 22 7月, 2016 6 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Stan Hu 提交于
We were seeing a number of error messages when attempting to create a keep-around ref: 1. Failed to create locked file `refs/keep-around/XYZ`: File exists 2. Failed to write reference `refs/keep-around/XYZ`: a reference with that name already exists. I'm not sure how these happen, but I suspect when multiple workers attempt to write the same file we may have an issue. The force parameter should help ensure the file gets created, as well as the rescues to prevent 500 Errors. Rugged/libgit2 unfortunately do not allow you to delete or re-create a reference that has been corrupted, even with the force parameter. Closes #20109
-
由 Achilleas Pipinellis 提交于
-
由 Alejandro Rodríguez 提交于
-
由 Annabel Dunstone 提交于
-
由 Annabel Dunstone 提交于
-
- 21 7月, 2016 11 次提交
-
-
由 Annabel Dunstone 提交于
-
由 Annabel Dunstone 提交于
-
由 Annabel Dunstone 提交于
-
由 Annabel Dunstone 提交于
-
由 Annabel Dunstone 提交于
-
由 Annabel Dunstone 提交于
-
由 Annabel Dunstone 提交于
-
-
Replace invocation of `find` with Ruby code that matches old cached files in a better, and safe way to avoid data-integrity issues.
-
由 Timothy Andrew 提交于
1. Instead, use `@page.title`, since it's always guaranteed to be around in a wiki. 2. `params[:id]` is _not_ always guaranteed to be around - if a page is created with errors, `render :edit` is called, and `params[:id]` is `nil`. 3. More context: https://gitlab.com/gitlab-org/gitlab-ce/issues/20079#note_13223240
-
由 Phil Hughes 提交于
-