<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/gitlab/gitlab-ce.git/spec/javascripts/matchers.js, branch frozen_string_lib_2</title>
<subtitle>gitlab.com: gitlab-org/gitlab-ce.git
</subtitle>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/gitlab/gitlab-ce.git/'/>
<entry>
<title>Comply with `no-implicit-coercion` rule (CE)</title>
<updated>2019-06-03T22:51:02+00:00</updated>
<author>
<name>Nathan Friend</name>
<email>nathan@gitlab.com</email>
</author>
<published>2019-06-03T22:51:02+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/gitlab/gitlab-ce.git/commit/?id=bee3c7e847e4c682f3b808ebfddcc0b6746c2d60'/>
<id>bee3c7e847e4c682f3b808ebfddcc0b6746c2d60</id>
<content type='text'>
This commit is the result of running `yarn eslint --fix` after enabling
the `no-implicit-coercion` ESLint rule.  This rule has been added to
our ESLint config here:

https://gitlab.com/gitlab-org/gitlab-eslint-config/merge_requests/14
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This commit is the result of running `yarn eslint --fix` after enabling
the `no-implicit-coercion` ESLint rule.  This rule has been added to
our ESLint config here:

https://gitlab.com/gitlab-org/gitlab-eslint-config/merge_requests/14
</pre>
</div>
</content>
</entry>
<entry>
<title>Make favicon tests more fault resistent</title>
<updated>2019-01-21T19:48:55+00:00</updated>
<author>
<name>Lukas Eipert</name>
<email>leipert@gitlab.com</email>
</author>
<published>2018-10-30T11:46:44+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/gitlab/gitlab-ce.git/commit/?id=91df6d9ef496bdab9fa3658b8dea131fb0a71c8c'/>
<id>91df6d9ef496bdab9fa3658b8dea131fb0a71c8c</id>
<content type='text'>
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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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.
</pre>
</div>
</content>
</entry>
<entry>
<title>Changes tab VUE refactoring</title>
<updated>2018-06-21T12:22:40+00:00</updated>
<author>
<name>Felipe Artur</name>
<email>fcardozo@gitlab.com</email>
</author>
<published>2018-06-21T12:22:40+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/gitlab/gitlab-ce.git/commit/?id=3e66795ef1ff1228906239763910b051d8afcc37'/>
<id>3e66795ef1ff1228906239763910b051d8afcc37</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Projects and groups badges settings UI</title>
<updated>2018-04-08T10:20:05+00:00</updated>
<author>
<name>Francisco Javier López</name>
<email>fjlopez@gitlab.com</email>
</author>
<published>2018-04-08T10:20:05+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/gitlab/gitlab-ce.git/commit/?id=31dd86b636a42e251e346dd5207281fda99c413f'/>
<id>31dd86b636a42e251e346dd5207281fda99c413f</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
