https://github.com/devopshobbies/devopshobbies-semver
https://github.com/devopshobbies/devopshobbies-semver
Last synced: about 1 month ago
JSON representation
- Host: GitHub
- URL: https://github.com/devopshobbies/devopshobbies-semver
- Owner: devopshobbies
- Created: 2023-04-26T15:33:41.000Z (almost 2 years ago)
- Default Branch: main
- Last Pushed: 2023-04-26T15:37:33.000Z (almost 2 years ago)
- Last Synced: 2025-01-25T07:09:42.736Z (3 months ago)
- Size: 2 MB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Main & Develop conventional release action
This is very simple but efficient, push into `develop` branch then you will have a patch release, push into `main` branch then you can have `minor` & `major` release.
## How to setup?
use the example below or the [release.yml](./.github/workflows/release.yml) file inside `.github` directory.
```yml
name: Release
on:
push:
branches:
- main
- develop
jobs:
next-version:
permissions: write-all
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
- name: Checkout code
uses: actions/checkout@8e5e7e5ab8b370d6c329ec480221332ada57f0ab
with:
fetch-depth: 0
# Do not use versions below 1.6.0
- name: Release
uses: mehdi-ra/[email protected]
with:
token: ${{secrets.GITHUB_TOKEN}}
releaseTitle: Auto release
```
## Inputs
| name | required | description |
| ------------ | -------- | ------------------------------- |
| token | true | Token for making release |
| releaseTitle | false | Title of releases |
| repository | false | where to get latest tag version |
## Outputs
| name | description |
| -------------- | ------------------------ |
| releaseVersion | Token for making release |
## Version fall back
If the action does not detect any change then creates a release with tag `v0.1.0`