semantic-release/semantic-release

ERELEASEBRANCHES: log a useful error message if the default release branch does not exist on remote

Open

#1.645 aberto em 1 de out. de 2020

Ver no GitHub
 (5 comments) (6 reactions) (1 assignee)JavaScript (1.638 forks)batch import
help wanted

Métricas do repositório

Stars
 (19.681 stars)
Métricas de merge de PR
 (Mesclagem média 3h 15m) (33 fundiu PRs em 30d)

Description

This is a follow up to https://github.com/semantic-release/semantic-release/issues/1643#issuecomment-702013702

New feature motivation

When I configure the branches setting to e.g. "release", but the release branch does not exist on remote, the error message is currently

✖  ERELEASEBRANCHES The release branches are invalid in the `branches` configuration.
A minimum of 1 and a maximum of 3 release branches are required in the branches configuration.

This may occur if your repository does not have a release branch, such as master.

Your configuration for the problematic branches is []

It should instead be something like this

✖  ERELEASEBRANCHES The default release branch ("release") does not exist on remote https://github.com/vantik/webapp.git. Create the branch and try again

New feature description

See above

New feature implementation

🤷🏼


If anyone is interested in contributing, this would be a great issue to start. Create a pull request with a failed test first, we can take the discussion from there. Comment below if you want to work on it

Guia do colaborador