moorara / cherry Goto Github PK

Context

Use Case

Proposed Solution

Alternative Solution

Description

Cherry should be able to read core settings (like GitHub token) from a global config file.
This config file can be saved in user home directory (.cherry.yaml).

• Rename Spec to Config
• .cherry file for core settings
• set command for core settings

Current Behavior

Expected Behavior

Proposed Solution

Description

A notify sub-command can be used for sending notifications (deployment, ...) to popular services such as Slack, Rollbar, etc.

Current Behavior

Expected Behavior

Example usages:

cherry notify slack <args>
cherry notify rollbar <args> 

Proposed Solution

For release commit (with message Releasing ...), when the build triggers binaries are not yet uploaded to the release, so the install.sh fails.

Description

Current Behavior

Expected Behavior

Proposed Solution

Description

• Release from master branch
• Release from release branches

Current Behavior

Expected Behavior

Proposed Solution

Description

Current Behavior

Expected Behavior

Proposed Solution

Current released version commit and next version commit are pushed on top of each other, so the CI build won't get trigged!

Context

Currently, cherry starts the release process and if something goes wrong, the release process fails and leaves the repo in a bad state (new commit, new tag, etc.)

How To Reproduce

Expected Behavior

Cherry needs run all pre-flight checks before start making any changes. In case of release command, these checks will be:

• Check if a GitHub token is set.
• Check if GitHub APIs can be reached and required permissions are provided.
• Check if dependencies such as github_changelog_generator are ready.

Proposed Solution

The following tools need to be available on Docker image:

• go
• git
• github_changelog_generator

Context

Cherry uses unannotated git tags for releasing.
Unannotated tags can change and changes the semantic of a release.

How To Reproduce

Expected Behavior

Proposed Solution

Use git tag -a ... for creating annotated tags.

Context

Use Case

Proposed Solution

go build -ldflags="-w -s"

NOTE: using these flags although disable the ability to use the pprof tool.

Alternative Solution

Example Usage:

go_versions:
    - 1.12
    - 1.14.6

Description

Current Behavior

Expected Behavior

Proposed Solution

Context

runtime.Version returns the version that the cherry binary is compiled with and not the version that is used from command-line to compile a new binary!

How To Reproduce

Expected Behavior

Proposed Solution

Use go version command output.

Linting checks should be run on every PR.

Implement a command to self-update cherry!

When running cherry from $PATH, the absolute path of binary is not resolved properly.

Description

Current Behavior

Expected Behavior

Proposed Solution