This is a fork from Klemensas/action-autotag for Flutter application.
This action will read a pubspec.yaml file and compare the version attribute to the project's known tags. If a corresponding tag does not exist, it will be created.
Usually, the version number is three numbers separated by dots, followed by an optional build number separated by a +, such as 1.2.21+7. The optional build number is ignored when the tag is created.
This tag works well in combination with:
- actions/create-release (Auto-release)
- author/action-publish (Auto-publish JavaScript/Node modules)
- author/action-rollback (Auto-rollback releases on failures)
- author/template-cross-runtime (a cross-runtime JavaScript repo template)
The following is an example .github/workflows/main.yml that will execute when a push to the main branch occurs.
name: Create Tag
on:
push:
branches:
- main
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: jacopocarlini/action-autotag@stable
with:
GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"To make this work, the workflow must have the checkout action before the autotag action.
This order is important!
- uses: actions/checkout@v2
- uses: jacopocarlini/action-autotag@stableIf the repository is not checked out first, the autotagger cannot find the pubspec.yaml file.
The GITHUB_TOKEN must be passed in. Without this, it is not possible to create a new tag. Make sure the autotag action looks like the following example:
- uses: jacopocarlini/action-autotag@stable
with:
GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"The action will automatically extract the token at runtime. DO NOT MANUALLY ENTER YOUR TOKEN. If you put the actual token in your workflow file, you'll make it accessible (in plaintext) to anyone who ever views the repository (it will be in your git history).
There are several options to customize how the tag is created.
-
package_rootBy default, autotag will look for the
pubspec.yamlfile in the project root. If the file is located in a subdirectory, this option can be used to point to the correct file.- uses: Klemensas/action-autotag@stable with: GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}" package_root: "/path/to/subdirectory"
-
tag_prefixBy default in flutter, the version number is three numbers separated by dots, followed by an optional build number separated by a +, such as
1.2.21+7. The optional build number is ignored when the tag is created. A prefix can be used to add text before the tag name. For example, iftag_prefixis set tov, then the tag would be labeled asv1.0.0.- uses: Klemensas/action-autotag@stable with: GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}" tag_prefix: "v"
-
tag_suffixText can also be applied to the end of the tag by setting
tag_suffix. For example, iftag_suffixis(beta), the tag would be1.0.0 (beta). Please note this example violates semantic versioning and is merely here to illustrate how to add text to the end of a tag name if you really want to.- uses: Klemensas/action-autotag@stable with: GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}" tag_suffix: " (beta)"
-
tag_messageThis is the annotated commit message associated with the tag. By default, a changelog will be generated from the commits between the latest tag and the new tag (HEAD). Setting this option will override it witha custom message.
- uses: Klemensas/action-autotag@stable with: GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}" tag_message: "Custom message goes here."
-
changelog_structureProvide a custom changelog format when not using
tag_message. This can interpolate strings, supported strings are{{message}},{{messageHeadline}},{{author}}and{{sha}}. Defaults to**{{message}}** {{sha}})\n.- uses: Klemensas/action-autotag@stable with: GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}" changelog_structure: "**{{messageHeadline}}** {{author}}\n"
-
versionExplicitly set the version instead of automatically detecting from
pubspec.yaml. Useful for non-Flutter projects where version may be output by a previous action.- uses: Klemensas/action-autotag@stable with: GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}" version: "${{ steps.previous_step.outputs.version }}"
If you are building an action that runs after this one, be aware this action produces several outputs:
tagnamewill be empty if no tag was created, or it will be the value of the new tag.tagsha: The SHA of the new tag.taguri: The URI/URL of the new tag reference.tagmessage: The messge applied to the tag reference (this is what shows up on the tag screen on Github).versionwill be the version attribute found in thepubspec.yamlfile.
Forked by Klemensas
This action was originally created by Corey Butler.