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

Hi guys,

Thank you for this awesome library!

Not sure if it's a bug or just me doing something wrong (probably the latter...), but I am experiencing some weird rendering issues when using the line layer.

At the maximum zoom level the line looks as I would expect it:

However, whe

MGLTilePyramidOfflineRegion should have a countOfTiles method that returns the number of tiles included in the tile pyramid. The implementation would rely on the mbgl::util::tileCount() function added in #9906.

This is the iOS/macOS equivalent to #11108 for Android. It would serve as a built-in alternative to mapbox/turf-swift#47 for applications already using the map SDK, including applica

Let's add MinVer and on successful builds generate a release.

We noticed that we have some common patterns for common conflicts/duplicate resolution in our monorepo across different binaries.
Like

  deploy_jar_rules=jar_rules(rules=[
    Duplicate('^BUILD', Duplicate.SKIP),
    Duplicate('^META-INF/ASL2.0', Duplicate.SKIP),
    Duplicate('^META-INF/INDEX.LIST', Duplicate.SKIP),
    Duplicate('^META-INF/io.netty.versions.properties', Duplicate.SKIP

In packages/components-typescript/package.json the fields main and main:src: refer to files that do not exist:

  "main": "src/index.tsx",
  "main:src": "src/index.tsx",

The index.tsx file is located in packages/components-typescript/index.tsx

Are these two fields redundant?

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

orgname/reponame is very common

I left a review and then got this message

which seems strange as it's telling me something I know.

This meta issue contains various ideas that may never be implemented, it's a good place to put things that could create useless noise in the issues section

Doc

• add various demonstration gifs in README.md files (#2080)
• add graphs (flow, DAG) to explain some particular parts

Code Quality

• switch moment.js usage to day.js and remove moment.js (#2174)

Bots

Which will behave like that

let settings = await prettyConfig('rollup', { configFiles })

if (!settings) {
  settings = await prettyConfig('rolldown', { configFiles })
}
console.log(settings)

instead of above we can hide it to look like that

const settings = await prettyConfig(['rollup', 'rolldown'], { configFiles })

if (!settings) {
  console.log('no config file