Semantically release to NPM
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
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.
Description
We currently have semantic release setup for the python package. When this occurs, also semantically release the frontend project to NPM.
- Dominant language
- Python
- Stars
- 1
- Forks
- 4
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 8
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openedx/sample-plugin
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
openedx/sample-plugin#46 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
openedx/sample-plugin#65 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 56/100
openedx/sample-plugin#51 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
openedx/sample-plugin#50 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 32/100
openedx/sample-plugin#33 ·
All issues in openedx/sample-plugin
Similar issues
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DiamondLightSource/dodal#2211 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openml/openml-python#1749 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sipyourdrink-ltd/bernstein#6191 ·