- 16 5月, 2017 8 次提交
-
-
由 Douwe Maan 提交于
Rename `build_events` to `job_events` Closes #31620 See merge request !11287
-
由 Winnie Hellmann 提交于
-
由 Douwe Maan 提交于
-
由 Jacopo 提交于
Flash error messages disappear(`fadeOut`) automatically after any successful request
-
由 Douwe Maan 提交于
This reverts merge request !11287
-
由 David Turner 提交于
Sometimes it is useful to store submodules in the same repository which contains links to them. Make the UI support this. See https://github.com/twosigma/git-meta/wiki/The-Omega-Repo for information about this strategy Signed-off-by: NDavid Turner <novalis@novalis.org>
-
由 Pawel Chojnacki 提交于
-
-
- 15 5月, 2017 13 次提交
-
-
由 Bob Van Landuyt 提交于
-
由 Kushal Pandya 提交于
-
由 George Andrinopoulos 提交于
-
由 Jacob Vosmaer (GitLab) 提交于
-
由 Bob Van Landuyt 提交于
From this point, the `services` table doesn't have the `build_events` flag anymore. So instead of updating the spec for this, I removed it. It should have been executed at this point.
-
由 Bob Van Landuyt 提交于
-
由 Valery Sizov 提交于
-
由 Valery Sizov 提交于
-
由 Jacob Vosmaer 提交于
-
由 Jacob Vosmaer 提交于
It seems that bad things happen when two gRPC stubs share one gRPC channel so let's stop doing that. The downside of this is that we create more gRPC connections; one per stub.
-
由 Z.J. van de Weg 提交于
When the owner of a pipelines schedule was either blocked or was removed from the project, the pipeline schedular would still schedule the pipeline. This would than fail however, given the user had no access to the project and it contents. However, a better way to handle it would be to not schedule it at all. Furthermore, from now on, such schedules will be deactivated so the schedule worker can ignore it on the next runs.
-
由 Luke "Jared" Bennett 提交于
-
由 Lin Jen-Shin 提交于
-
- 14 5月, 2017 2 次提交
-
-
由 Luke "Jared" Bennett 提交于
-
由 Ahmad Sherif 提交于
Closes gitaly#199
-
- 13 5月, 2017 12 次提交
-
-
由 Simon Knox 提交于
change all .nav-links to use flex place Resolve Discussions above tabs on small screens, and to the right on large
-
由 Gabriel Mazetto 提交于
-
由 Gabriel Mazetto 提交于
-
由 Gabriel Mazetto 提交于
-
由 Gabriel Mazetto 提交于
-
由 Douwe Maan 提交于
-
由 Annabel Dunstone Gray 提交于
-
由 Stan Hu 提交于
See http://rubular.com/r/uTDlT85zW1
-
由 Sean McGivern 提交于
I don't know why this happens exactly, but given an upstream and fork repository from a customer, both of which required GC, resolving conflicts would corrupt the fork so badly that it couldn't be cloned. This isn't a perfect fix for that case, because the MR may still need to be merged manually, but it does ensure that the repository is at least usable. My best guess is that when we generate the index for the conflict resolution (which we previously did in the target project), we obtain a reference to an OID that doesn't exist in the source, even though we already fetch the refs from the target into the source. Explicitly setting the source project as the place to get the merge index from seems to prevent repository corruption in this way.
-
由 Luke "Jared" Bennett 提交于
-
由 Douwe Maan 提交于
-
由 Pawel Chojnacki 提交于
-
- 12 5月, 2017 5 次提交
-
-
由 Bob Van Landuyt 提交于
For exact matches, not namespaces that end with an invalid path
-
由 Douwe Maan 提交于
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Douwe Maan 提交于
-
由 Yorick Peterse 提交于
By adding the default value _after_ adding the column we avoid updating all rows in a table, saving a lot of time and unnecessary work in the process.
-