cli
cli copied to clipboard
:cl::round_pushpin: Setup automated semver compliant package publishing
``` $ semantic-release-cli setup ? What is your npm registry? https://registry.npmjs.org/ ? What is your npm username? rslemos ? What is your npm password? [hidden] ? What is your GitHub...
If you use the semantic-release CLI to setup `semantic-release` in a GitHub repository, then you probably receive an E-Mail from GitHub with the subject "[GitHub] Deprecation Notice", stating that >...
## Current behavior Message from Github after running `npx semantic-release setup` > Hi @abhisekp, > > On July 10th, 2020 at 07:50 (UTC) you or an application you used recently...
https://github.com/semantic-release/cli/blob/8083cc0acd839a0bc279bb3691b6388106ff7242/src/lib/github.js#L46 https://github.com/semantic-release/cli/blob/a5910c91399ad5b6828ed7e631338de0a86d62b2/src/lib/github.js#L49
I have noticed that Github action doesn't support `[skip ci]` feature yet, so when you setup your CI with semantic release, this will trigger the action twice, a workaround solution...
`semantic-release-cli` version being used - 5.3.0 Tried option of `setup` and `init`, error is same. `ERR! semantic-release Sorry, we experienced an error. ERR! semantic-release ERR! semantic-release request_id:e5785f3d5458a5dad347e31a21ccbf7b ERR! semantic-release error...
## New feature motivation On May 6th, 2020 at 10:18 (UTC) you or an application you used recently accessed the deprecated Authorizations endpoint on the GitHub API with the useragent...
## The dependency [npm](https://github.com/npm/cli) was updated from `6.13.1` to `6.13.2`. 🚨 [View failing branch](https://github.com/semantic-release/cli/compare/master...semantic-release:greenkeeper%2Fnpm-6.13.2). This version is **covered** by your **current version range** and after updating it in your project...
My repo is on Azure Repos, and the `git remote -v` command gives the following: ```sh origin [email protected]:v3/org/project/repo (fetch) origin [email protected]:v3/org/project/repo (push) ``` When runnint `semantic-release`, I generate a `CHANGELOD.md`...
Similar to my other feature request, is it absolutely fundamental that semantic-release-cli work exclusively via Github, or is it possible to add support for other cloud SCM platforms, such as...