skills.rest
ealvar3z
ealvar3zCOMMUNITY
Explore all skills by this author →
Website𝕏@bruno_jenkinzGitHub

increment-version-and-push

Increment semantic versions in Go projects and push git tags.

Updated Dec 3, 2023
Search Tags:#automation#git#versioning#deployment#go#release
One-click install
npx skills add https://github.com/ealvar3z/dotfiles --skill increment-version-and-push
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: increment-version-and-push
Source: https://github.com/ealvar3z/dotfiles/tree/main/prompts/skills/increment-version-and-push
Command: npx skills add https://github.com/ealvar3z/dotfiles --skill increment-version-and-push

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of updating a project's version, creating a git tag for that version, committing the change, and pushing both the commit and the tag to the remote repository.

Core Features & Use Cases

  • Version Bumping: Supports semantic versioning (major.minor.patch) with clear rules for incrementing each part.
  • Git Integration: Creates git tags and commits, ensuring version history is tracked.
  • Push Automation: Pushes the tagged commit to the remote repository.
  • Use Case: After completing a new feature, use this skill to increment the minor version, tag the release, commit the change, and push it to GitHub.

Quick Start

Use the increment-version-and-push skill to bump the patch version of the project and push the changes.

Frequently Asked Questions about increment-version-and-push

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate bumping a Go project version and pushing the git tag?▼

To automate Go project version bumping and pushing git tags, this Skill updates the internal/version.go file, creates a semantic version git tag, commits the change, and pushes both to your remote repository.

What is the best way to increment semantic versions for a release commit?▼

Incrementing semantic versions for a release commit is handled by updating the major, minor, or patch number based on your specified rules, ensuring version history is tracked through git tags.

Does this version bumping automation work with non-Go projects?▼

No, this version bumping automation specifically targets Go-based projects by locating and updating the internal/version.go file, so it does not apply to non-Go projects.

How do I push a new git tag and commit to a remote repository after a feature release?▼

Pushing a new git tag and commit to a remote repository after a feature release is done by committing the version change locally, creating a git tag for the new version, and pushing both to the remote.

Do I need to manually create git tags when using automated versioning?▼

No, you do not need to manually create git tags when using automated versioning, as the process simultaneously increments the version, creates the git tag, commits, and pushes to the remote.

Related Skills

Explore More Software Engineering Skills→
gonzalezpazmonicagonzalezpazmonica
47

savia-hub-sync

Synchronize SaviaHub repositories between local and remote instances with Git.

Community
Advanced
Conceptual-MachinesConceptual-Machines
195

release

Create and push a v-prefixed git tag on the main branch.

Official
Intermediate
peterfeipeterfei
420

changelog-generator

Generate CHANGELOG.md from Git commit history using Conventional Commits.

Community
Intermediate
heyu-aiheyu-ai

bump-version

Automate version bumping, CHANGELOG generation, and Git tagging across project files.

Official
Advanced