{"repo":"pkgdeps/git-tag-action","free":true,"listed":false,"github":"https://github.com/pkgdeps/git-tag-action","clone":"git clone https://github.com/pkgdeps/git-tag-action.git","description":"[GitHub Action] Get ${version} from package.json and git tag ${version} for the repository.","language":"TypeScript","stars":30,"topics":["github-actions","git","tag","releases"],"license":"MIT","category":"workflow-automation","readme_excerpt":"pkgdeps/git-tag-action This action do git tag ${version} to the repository, but it is idempotent. - Push the tag if the tag does not exist on the repository Usage You create workflow file like .github/workflows/publish.yml . UseCase 1. [Manual] Update Version: npm --no-git-tag-version version {patch,minor,major} 2. [Manual] Push: git push --tags or Merge the Pull Request 3. [CI] Publish to npm and Push a tag to GitHub This Release flow is defined in .github/workflows/publish.yml For more details, see following example - azu/npm-github-package-example: npm registry to GitHub Package Registry example. Options Release 1. https://github.com/pkgdeps/git-tag-action 2. Create new tag like \"v2.0.0\" 3. CI publish \"v2.0.0\", \"v2.0\", and \"v2\" CHANGELOG - 2.0.0: tag is annotated tag instead of lightweight tag - Rename action-package-version-to-git-tag to git-tag-action Reference - GitHub Actionsでnpmに自動でリリースするworkflowを作ってみた ｜ Developers.IO FAQ Error: npm ERR! code E401 Occur following error: Please check NODE AUTH TOKEN","default_branch":null,"files":null,"tree":[],"storefront":"/r/pkgdeps","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/pkgdeps/git-tag-action/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}