An error occurred fetching the project authors.
- 14 Jan, 2016 4 commits
-
-
Douwe Maan authored
Allow broadcast messages to be edited Closes #3046 See merge request !2268
-
Dmitriy Zaporozhets authored
Update button style on milestone pages See merge request !2414
-
Achilleas Pipinellis authored
Update documentation to Go 1.5.3 Security fix: https://groups.google.com/forum/#!topic/golang-dev/MEATuOi_ei4 See merge request !2418
-
Stan Hu authored
-
- 13 Jan, 2016 36 commits
-
-
Robert Speicher authored
-
Robert Speicher authored
-
Grzegorz Bizon authored
Fix has been introduced in !2224.
-
Achilleas Pipinellis authored
Move doc_styleguide in the development directory Reference #3841 And also add many new styleguides: - Naming - Images - Links - Headings - Formatting - Notes - API See merge request !2386
-
Drew Blessing authored
Added hint that you can search users by name, username, or email. Fixes gitlab-org/gitlab-ee#19 /cc @JobV See merge request !2411
-
Achilleas Pipinellis authored
- Fix some syntax/grammar typos - Link to GFM documentation on newlines - Be less strict on the alphabetical order styleguide - You can override the "numbers in headings" rule if you discuss it first - Do not mention CE in notes if the feature is in both CE and EE
-
Robert Speicher authored
-
Robert Speicher authored
-
Robert Speicher authored
[ci skip]
-
Robert Speicher authored
Closes #3046
-
Robert Speicher authored
- Removes redundant "Create a broadcast message" scenario that was entirely covered by the "Create a customized broadcast message" scenario. - Adds "Edit an existing broadcast message" scenario - Adds "Remove an existing broadcast message" scenario
-
Robert Speicher authored
- Adds default values for `color` and `font` attributes - Adds `active?`, `started?`, `ended?`, and 'status' methods
-
Robert Speicher authored
Now it returns the fully-formatted message so we can be consistent about how it's shown.
-
Robert Speicher authored
Also make the feature tests less brittle.
-
Robert Speicher authored
Also resets the default example message when the user input is blank.
-
Robert Speicher authored
-
Robert Speicher authored
-
Robert Speicher authored
-
Robert Speicher authored
-
Patricio Cano authored
-
Yorick Peterse authored
See merge request !2406
-
Douwe Maan authored
Fix #9963 reference_filter "Encoding::CompatibilityError" bug with some complex URL; https://github.com/gitlabhq/gitlabhq/pull/9964 @DouweM See merge request !2383
-
Jason Lee authored
-
Douwe Maan authored
Extend projects API with CI data Reference #4264 See merge request !2303
-
Douwe Maan authored
enable milestone filter to stick See merge request !2241
-
Yorick Peterse authored
Sampling data at a fixed interval means we can potentially miss data from events occurring between sampling intervals. For example, say we sample data every 15 seconds but Unicorn workers get killed after 10 seconds. In this particular case it's possible to miss interesting data as the sampler will never get to actually submitting data. To work around this (at least for the most part) the sampling interval is randomized as following: 1. Take the user specified sampling interval (15 seconds by default) 2. Divide it by 2 (referred to as "half" below) 3. Generate a range (using a step of 0.1) from -"half" to "half" 4. Every time the sampler goes to sleep we'll grab the user provided interval and add a randomly chosen "adjustment" to it while making sure we don't pick the same value twice in a row. For a specified timeout of 15 this means the actual intervals can be anywhere between 7.5 and 22.5, but never can the same interval be used twice in a row. The rationale behind this change is that on dev.gitlab.org I'm sometimes seeing certain Gitlab::Git/Rugged objects being retained, but only for a few minutes every 24 hours. Knowing the code of Gitlab and how much memory it uses/leaks I suspect we're missing data due to workers getting terminated before the sampler can write its data to InfluxDB.
-
Yorick Peterse authored
-
Dmitriy Zaporozhets authored
merge request close message moved and merge request now refered by `!`. Fixes #4161 ![Screen_Shot_2016-01-12_at_8.38.57_AM](/uploads/9390ce0ebd1d14bfc83130ff4913a823/Screen_Shot_2016-01-12_at_8.38.57_AM.png) See merge request !2387
-
Dmitriy Zaporozhets authored
Disable colorization if STDOUT is not a tty Closes #6118 See merge request !2403
-
Dmitriy Zaporozhets authored
Block the reported user before destroying the record This is intended to prevent the user from creating new objects while the transaction that removes them is being run, resulting in objects with nil authors which can then not be edited. See https://gitlab.com/gitlab-org/gitlab-ce/issues/7117 See merge request !2402
-
Dmitriy Zaporozhets authored
Make sure time_ago_with_tooltip is using a Time object Somehow this test existed on EE but not in CE, so it started failing after a bad CE-to-EE merge. See merge request !2398
-
Dmitriy Zaporozhets authored
Comment and close button does not submit comment See merge request !2399
-
https://github.com/tbeadle/gitlabhqDmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Include the user_id in user_*_team system hooks.
-
Stan Hu authored
Mention channel/key bug in irkerd docs
-
Robert Speicher authored
It patches core classes (such as String) to add colorization methods like `red` which we can't disable the same way we can with the Colorization gem.
-