openedx / openedx/sample-plugin

Semantically release to NPM

Open
#23 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1
Forks
4
Avg merge
3d 1h
Merged PRs (30d)
8

Description

We currently have semantic release setup for the python package. When this occurs, also semantically release the frontend project to NPM.

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

Start by locating the existing semantic-release setup for the Python package and the frontend project's package metadata or release entry point; the issue names no files or tests. Determine how the current release is triggered, then verify that the frontend is published to NPM in the same release flow.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.