Automated Release

Open
#30 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the repository's existing GitHub Actions configuration and package scripts, then compare them with the proposed workflow. Check how yarn test, yarn prepare, and semantic-release would run on pushes to main, including the required GitHub and npm tokens. Done means releases are automated without breaking the existing test and preparation steps.

Written by the indexing model from the issue text.

Description

dev-ops feature-request

What about automated releases?
Every commit to main branch can be a new version

Workflow:

name: release
on: push

jobs:
  release:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v1
        with:
          node-version: 14.x

      - run: yarn install
      - run: yarn test
      - run: yarn prepare

      - name: Release
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
        run: npx semantic-release --branches main
Dominant language
TypeScript
Stars
2.6k
Forks
136
Avg merge
5d 4h
Merged PRs (30d)
12

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.

More from margelo/react-native-graph

All issues in margelo/react-native-graph

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.