using shell to evaluate env or expressions

Open
#528 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, shell
Domain
release

Research direction

No source files, tests, or entry points are named. Begin by locating the plugin's message configuration and package.json handling, then treat shell evaluation or placeholders and the two requested default-message changes as the completion criteria.

Written by the indexing model from the issue text.

Description

1- if the package support shell, we can do something like that

 [
     
        '@semantic-release/git',
        {
          message:
            "build: release $(jq -r '.name' package.json)-${nextRelease.version} [skip ci]",
        },
      ]

2- we can provide ${ package } placeholder, so we can do something like "build: release${ package.name }-..."

3- apart from supporting shell, we need to change the default message:

  • remove "${ nextRelease.notes }", because it often violates commitLint rules
  • add package.name by default (useful for monorepos)
Dominant language
JavaScript
Stars
339
Forks
75
Avg merge
5h 15m
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from semantic-release/git

All issues in semantic-release/git

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.