This is an automated email from the ASF dual-hosted git repository.
amaranhao pushed a change to branch upgrade-to-eslint-v4
in repository https://gitbox.apache.org/repos/asf/couchdb-fauxton.git.
omit b2a855f Reverting because syntax is not valid in Node
omit f705bd3 More lint fixes after rebasing
omit 9223b69 Enforce no-else-return rule and fix issues
omit 3673570 Enforce 2-space indent rule and fix all issues
omit 4fa3a21 Address Garren's comments
omit c59243d Enable eslint-react recommended rules
omit 1c8bf8c Fix lint issues
omit 17541c0 Upgrade eslint to v4 with recommended config
add 93f4842 Fix documentation links in Fauxton (#1040)
new 19739f5 Upgrade eslint to v4 with recommended config
new 861a7c5 Fix lint issues
new 9cebf04 Enable eslint-react recommended rules
new ef13ad6 Address Garren's comments
new 63f738a Enforce 2-space indent rule and fix all issues
new 682facb Enforce no-else-return rule and fix issues
new 0f2e7ac More lint fixes after rebasing
new 922caa1 Reverting because syntax is not valid in Node
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (b2a855f)
\
N -- N -- N refs/heads/upgrade-to-eslint-v4 (922caa1)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 8 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
app/constants.js | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--
To stop receiving notification emails like this one, please contact
['"[email protected]" <[email protected]>'].
