https://github.com/simonrjones/test-auto-version

Test repo to test automatic versioning / code releases
https://github.com/simonrjones/test-auto-version

Last synced: 18 days ago
JSON representation

Test repo to test automatic versioning / code releases

• Host: GitHub
• URL: https://github.com/simonrjones/test-auto-version
• Owner: simonrjones
• License: mit
• Created: 2022-07-02T11:17:31.000Z (over 2 years ago)
• Default Branch: main
• Last Pushed: 2022-10-05T14:12:43.000Z (about 2 years ago)
• Last Synced: 2024-10-19T14:20:24.261Z (29 days ago)
• Language: PHP
• Homepage:
• Size: 57.6 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# test-auto-version

A test repo to test how release-please works. Testin 1, 2, 3.

Download the [latest release file](https://github.com/simonrjones/test-auto-version/releases/latest/download/amplify.zip).

## Creating new releases

This repo uses [Release Please](https://github.com/marketplace/actions/release-please-action) to automatically create releases, based on [semantic versioning](https://semver.org/).

To create a new release use [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) in your commit message. This will automatically create a Release PR, which is kept up to date with further commits and you can merge it to create the new release when you are ready.

Use the following keywords in your commits:

* `fix:` this indicates a bug fix and creates a new patch version (e.g. 1.0.1).

* `feat:` this indicates a new feature and creates a new minor version (e.g. 1.1).

* To create a new major version (e.g. 2.0.0) either append an exclamation mark to `fix!:` or `feat!:` or add a footer of `BREAKING CHANGE:` with details of what breaking changes there are.

If the action fails to run you can view the action and select `Re-run all jobs` to re-run it.