💅 For consistent CSS across BigchainDB, IPDB, Ocean Protocol & ascribe's repos. https://www.bigchaindb.com
Go to file
Matthias Kretschmann 5fee44d71a
Merge pull request #23 from bigchaindb/greenkeeper/release-it-12.0.0
Update release-it to the latest version 🚀
2019-05-03 22:53:38 +02:00
media be more clear in the npm publish part, add instructions for flexibility 2017-05-31 20:59:18 +02:00
.editorconfig initial commit 2017-05-30 19:51:20 +02:00
.eslintrc initial commit 2017-05-30 19:51:20 +02:00
.gitignore initial commit 2017-05-30 19:51:20 +02:00
.travis.yml initial commit 2017-05-30 19:51:20 +02:00
index.js allow @include 2017-07-18 14:07:52 +02:00
license make license work with GitHub's license parser 2017-05-30 22:29:50 +02:00
package.json chore(package): update release-it to version 12.0.0 2019-05-03 19:05:22 +00:00
readme.md switch deprecated rules from example 2017-07-18 13:16:54 +02:00



💅 For consistent CSS across BigchainDB, IPDB & ascribe's repos. Extends on stylelint-config-standard

css bigchaindb js bigchaindb npm Build Status Greenkeeper badge

This cat clearly forgot to lint her CSS before deployment:

cat not linting correctly

Don't be like that cat.


npm install stylelint-config-bigchaindb



Add this to your .stylelintrc file:

    "extends": "stylelint-config-bigchaindb"

If you really know what you're doing™ you can change or disable individual rules globally in your project:

    "extends": "stylelint-config-bigchaindb",
    "rules": {
        "selector-max-id": 1,
        "selector-no-qualifying-type": null

Or disable blocks inline in your css:

/* stylelint-disable selector-list-comma-newline-after  */
h1, h2, h3, h4, h5, h6,
.h1, .h2, .h3, .h4, .h5, .h6 {
    color: $that-pink-which-burns-my-eyes;
/* stylelint-enable */

In general, try to never disable anything. Every time you disable even one rule one of those creatures gets killed:

disable punishment


Use stylelint against your css files, e.g.:

stylelint *.scss

Or lint in your editor with one of the many editor plugins for stylelint, e.g. for Atom:

apm install linter-stylelint

npm releases

For a new patch release, execute on the machine where you're logged into your npm account:

npm run release

Command is powered by release-it package, defined in the package.json.

That's what the command does without any user interaction:

  • create release commit by updating version in package.json
  • create tag for that release commit
  • push commit & tag
  • create a new release on GitHub, with change log auto-generated from commit messages
  • publish to npm as a new release

If you want to create a minor or major release, use these commands:

npm run release-minor
npm run release-major


Copyright 2017 BigchainDB GmbH

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.