Expected Behavior

It should be possible to customize the header of the generated changelog (or omit it completely).

Current Behavior

The changelog header is hardcoded in https://github.com/lerna/lerna/blob/master/core/conventional-commits/lib/constants.js

Possible Solution

A `command.publish.changelogHea

Environment

• Package version(s): @blueprintjs/core ^3.22.3
• Browser and OS versions: Mac OS X Chrome 79.0.3945.88

If possible, link to a minimal repro (fork this code sandbox):

Steps to reproduce

Spotted this while building a <ControlGroup> that contained buttons, selects, and some dividers.

`

Ref: https://gitmoji.carloscuesta.me/

如上这个 emoji commit message 指引感觉非常好，所以大致翻译了下和大家分享

出发点源于最近在梳理和制定一套标准化且规范化开发细则，其中如何管理 commit 就是其中很重要的一个环节

借鉴了 angular 开发的规范，目前也是比较大规模使用的。

在指引文档中其中有一点涉及

Subject
The subject contains succinct description of the change:

• use the imperative, present ten

package.json supports shortcut syntax for the repository field (https://docs.npmjs.com/files/package.json#repository)

orgname/reponame is very common

According to the Mongoose arrays documentation, an array default value is possible.
But in schm, when array of schema is validatate, the default value is always an empty array.

Inspired example from Mongoose

const ToySchema = schm({ name: String });
const ToyBoxSchema = schm({
  toys: {
    type: [ToySchema],
    defaul

Could you make a tutorial out of the content of this repo? How to assemble each part step by step.

Explicitly stating the file path for where a given code snippet should go is helpful to many docs readers. Right now most of the snippets have the file path as a comment at the top. For example:

// src/app/myFile.js

function stuff() {
...

However, some types of files do not support comments and will cause errors if a user copies the snippet and doesn't remove the commented fi

Description

Instead of playing "ask a bolty" when developers have questions about available sass constructs, can we use something like http://sassdoc.com/getting-started/ to generate documentation?

I've tried running it against a simple bolt entrypoint and it seems to work pretty well.

It would be very useful to be able to run yerna run build --include-path . --dependencies instead of manually specifying the current package name as a regex. This should use find-up from the provided path to find the closest package.json and include its name, but refusing to recurse out of packages.

Tried to use this package, but setup documentation was scarce. Ideally looking for details on how to set this up with a new yarn workspace. Things that are currently not clear:

• Exactly which project to install this package into (root or sub-projects)
• How and when to execute this before running flow.

Ideally maybe there can be just a single command to run that replaces yarn flow?

check if dupe package names in same folder cause issues - write a test that should capture this problem, only resolution is to ignore the path/folder that contains the dupe package(s).