delta/gitlab/gitlab-ce.git/spec/javascripts, branch hooks-ext gitlab.com: gitlab-org/gitlab-ce.git Merge branch '25569-changing-wording-to-delete-when-referring-to-removing-a-branch' into 'master' 2019-01-23T11:02:22+00:00 Filipa Lacerda filipa@gitlab.com 2019-01-23T11:02:22+00:00 3ed8078507b6cb37c7dd85f2fc22c9494faf9e1e Resolve "Changing wording to "Delete" when referring to removing a branch" Closes #25569 See merge request gitlab-org/gitlab-ce!23966 
Resolve "Changing wording to "Delete" when referring to removing a branch"

Closes #25569

See merge request gitlab-org/gitlab-ce!23966
 Merge branch 'dm-trim-discussion-truncated-line-first-chars' into 'master' 2019-01-23T08:45:17+00:00 Phil Hughes me@iamphill.com 2019-01-23T08:45:17+00:00 52ceda44798a8d987dff56695bb2f9e0f775c55f Fix bug that caused Suggestion Markdown toolbar button to insert snippet with leading +/-/<space> See merge request gitlab-org/gitlab-ce!24568 
Fix bug that caused Suggestion Markdown toolbar button to insert snippet with leading +/-/<space>

See merge request gitlab-org/gitlab-ce!24568
 Use 'delete' instead of 'remove' for source branch 2019-01-22T17:57:01+00:00 Sam Bigelow sbigelow@gitlab.com 2019-01-10T04:08:52+00:00 c607b358241712af0d6b442b8e7a277cb6ba8a38 This is to match `git branch -D <branchname>` 
This is to match `git branch -D <branchname>`
Trim first char of diff line text on diff discussions 2019-01-22T16:00:16+00:00 Douwe Maan douwe@selenight.nl 2019-01-22T12:35:28+00:00 03df54b226f63a05ee2229b9f7f1f3e90383430a Before, diff file `higlighted_diff_lines`/`parallel_diff_lines` and diff discussion `truncated_diff_lines` were inconsistent: `text` and `rich_text` on the latter included the leading +/-/<space> character, like on the backend, while the former had no `text` and its `rich_text` had dropped this char. This resulted in a bug when the suggestions feature expected these diff line objects to be identical in format and thus interchangeable, which was not the case. 
Before, diff file `higlighted_diff_lines`/`parallel_diff_lines` and
diff discussion `truncated_diff_lines` were inconsistent: `text` and
`rich_text` on the latter included the leading +/-/<space> character,
like on the backend, while the former had no `text` and its `rich_text`
had dropped this char.

This resulted in a bug when the suggestions feature expected these diff
line objects to be identical in format and thus interchangeable, which
was not the case.
Merge branch 'leipert-make-canvas-more-tolerant' into 'master' 2019-01-22T15:20:12+00:00 Phil Hughes me@iamphill.com 2019-01-22T15:20:12+00:00 7b6fa5ffcbead7c45c331df6d4c7a5352b6c3521 Make favicon tests more fault resistent Closes #50527 See merge request gitlab-org/gitlab-ce!22686 
Make favicon tests more fault resistent

Closes #50527

See merge request gitlab-org/gitlab-ce!22686
 Merge branch '53856-changing-group-visibility-does-not-re-enable-save-button' into 'master' 2019-01-22T10:41:01+00:00 Filipa Lacerda filipa@gitlab.com 2019-01-22T10:41:01+00:00 ed1da730202bf3178c43b3467635853733b799c1 Resolve "Changing group visibility does not re-enable Save button" Closes #53856 See merge request gitlab-org/gitlab-ce!23022 
Resolve "Changing group visibility does not re-enable Save button"

Closes #53856

See merge request gitlab-org/gitlab-ce!23022
 Resolve "Merge request file browser should always be possible show/hide" 2019-01-22T08:29:41+00:00 Sam Bigelow sbigelow@gitlab.com 2019-01-22T08:29:41+00:00 a0146dceb633ca459889fef80f72c5e2dd4db476 






Fix DirtySubmit handling of checkbox and radio inputs
2019-01-22T02:04:32+00:00

Luke Bennett
lbennett@gitlab.com

2018-11-14T19:51:39+00:00

88ce491fc981527ec864176e84332ecb7b8ac0ce

Most browsers do not fire the "input" event for checkboxes or radios.
Adds a "change" listener to properly trigger these DirtySubmit updates.





Most browsers do not fire the "input" event for checkboxes or radios.
Adds a "change" listener to properly trigger these DirtySubmit updates.







Make favicon tests more fault resistent
2019-01-21T19:48:55+00:00

Lukas Eipert
leipert@gitlab.com

2018-10-30T11:46:44+00:00

91df6d9ef496bdab9fa3658b8dea131fb0a71c8c

It seems like every new version of Chrome renders the favicon canvas
differently. This reduces the problems with it by creating a more fault
tolerant check, which compares the color values in the pixels and is
okay if they are within a certain threshold.





It seems like every new version of Chrome renders the favicon canvas
differently. This reduces the problems with it by creating a more fault
tolerant check, which compares the color values in the pixels and is
okay if they are within a certain threshold.







Resolve "Admin Settings: Cannot read property 'addEventListener' of null"
2019-01-21T12:39:11+00:00

Martin Wortschack
mwortschack@gitlab.com

2019-01-21T12:39:11+00:00

51a9c5492388a95ac82292333d068c6d1bab9d64