margelo / margelo/react-native-graph
Automated Release
Open
Nobody has claimed this yet.
dev-ops
feature-request
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 136
- Avg merge
- 5d 4h
- Merged PRs (30d)
- 12
Description
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
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.
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.
Assessment
- Tech stack
- github-actions, nodejs
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100