This action was deprecated on 2023-09-08 and will no longer receive support or updates.
This action pushes supplied tag values to the remote repository. It is only run for main/master branch builds; feature branches are skipped.
name: Create Git Tag
on: workflow_dispatch
jobs:
map-some-version:
runs-on: ubuntu-20.04
steps:
- name: Checkout
uses: actions/checkout@v3
- name: Map versions
id: map-versions
uses: im-open/omni-repo-version-map-action@v1
- name: Tag Project Versions
# You may also reference the major or major.minor version
uses: im-open/omni-repo-git-tag-action@v1.1.3
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
version_map: ${{ steps.map-versions.outputs.version_map }}| Parameter | Is Required | Description |
|---|---|---|
github_token |
Yes | Needed to generate and push release tags |
version_map |
Yes | A JSON object that maps projects to the tag to give them |
The version_map needs to have the following schema:
{
"Project Name": {
"tag": "The git tag you want to create"
}
}This is most easily generated in a previous step, such as with this versioning action.
When creating PRs, please review the following guidelines:
- The action code does not contain sensitive information.
- At least one of the commit messages contains the appropriate
+semver:keywords listed under Incrementing the Version for major and minor increments. - The action has been recompiled. See Recompiling Manually for details.
- The README.md has been updated with the latest version of the action. See Updating the README.md for details.
This repo uses git-version-lite in its workflows to examine commit messages to determine whether to perform a major, minor or patch increment on merge if source code changes have been made. The following table provides the fragment that should be included in a commit message to active different increment strategies.
| Increment Type | Commit Message Fragment |
|---|---|
| major | +semver:breaking |
| major | +semver:major |
| minor | +semver:feature |
| minor | +semver:minor |
| patch | default increment type, no comment needed |
The files and directories that are considered source code are listed in the files-with-code and dirs-with-code arguments in both the build-and-review-pr and increment-version-on-merge workflows.
If a PR contains source code changes, the README.md should be updated with the latest action version and the action should be recompiled. The build-and-review-pr workflow will ensure these steps are performed when they are required. The workflow will provide instructions for completing these steps if the PR Author does not initially complete them.
If a PR consists solely of non-source code changes like changes to the README.md or workflows under ./.github/workflows, version updates and recompiles do not need to be performed.
This command utilizes esbuild to bundle the action and its dependencies into a single file located in the dist folder. If changes are made to the action's source code, the action must be recompiled by running the following command:
# Installs dependencies and bundles the code
npm run buildIf changes are made to the action's source code, the usage examples section of this file should be updated with the next version of the action. Each instance of this action should be updated. This helps users know what the latest tag is without having to navigate to the Tags page of the repository. See Incrementing the Version for details on how to determine what the next version will be or consult the first workflow run for the PR which will also calculate the next version.
This project has adopted the im-open's Code of Conduct.
Copyright © 2023, Extend Health, LLC. Code released under the MIT license.