lerna / lerna/lerna

Ability to create a Github discussion thread when a release version published

Open
#3,678 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

accepting-prs type: feature
Dominant language
TypeScript
Stars
36.1k
Forks
2.3k
Avg merge
1d 4h
Merged PRs (30d)
50

Description

Description

When releasing a version, we have the option to --create-release github which creates a new Release in Github. When we create a Release manually in Github we have an option to Create a discussion for this release, but this is not possible currently with lerna command options.

Motivation

As GitHub added this feature relatively new, and manually we were able to create discussion, it is good to automate it during the release process

Suggested Implementation

To start with, add an option to lerna version command like --crerate-github-discussion which accepts a value of one of the Discussion types. This option should be applicable only when --create-release github option is passed

Alternate Implementations

Alternatively, add a property in lerna.json under the version command called createGithubDiscussion that accepts a boolean

Contributor guide

Open the contributing guide

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.

Research direction

Review the lerna version command and its existing --create-release github path, then compare them with the proposed lerna.json version configuration. Determine how a GitHub release discussion type should be selected and which interface is appropriate. Done means publishing a GitHub release can optionally create the requested discussion without affecting releases that do not enable the option.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, typescript
Domain
cli, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.