algolia / shipjs Goto Github PK

For consistency.
npx shipjs ...

at prepare command

When there was no token for publish, it failed, but exited with 0. It should fail the circle ci flow.

using versionUpdated hook

monorepo: {
  ...
  independentVersion: true
}

Independent versioning is okay-ish, because git log can be scoped to specific directory.

However, independent changelog is hard specially in independent versioning mode.
With independent versioning "OFF", an example of independent changelog can be this, but with it "ON", it makes it harder.

How can we achieve this?

• add "everything locally" section after "Installation".
• move "Integrate with CircleCI" section to "Useful Configurations"

This shouldn't look red.

It won't work. Hub isn't on circleci. Let's fix this documentation.

To be:
Flow: an array of steps

Think about the "prepare" flow and the different step that should take place when using independent versioning in monorepo and when it's not.

Now it's pushing only tags.
It should be something like git push && git push origin v0.1.2.

name = getBranchNameToMergeBack()

When there is no remote branch named name, it will fail.
So at the beginning of release, let's check it first, and exit with error if not exists.
User has to manually create the release branch because shipjs has no idea which is the latest released commit.

Merge branch 'master' of github.com:eunjae-lee/dummy-lib-1111

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Preset name not found within published preset config (monorepo:babel6). Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

https://github.com/eunjae-lee/dummy-lib-1111

publishCommand is defaultConfig for yarn is supposed to be yarn publish --no-git-tag-version --non-interactive.

add slack notification for success or failure.
(When shouldRelease return false, it exits with exitCode 0. This time, let's not send a notification.)

• license
• contributing
• github issue templates

defaultConfig doesn't need baseBranches. It can be inferred from mergeStrategy.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

It should have an option for dry run

extract functions from shipjs-cli and write tests for them

1. create a merge commit
2. squash and merge

toSameBranch: (2)
toReleaseBranch: (1)

-> it should be documented & added as a description in PR