A GitHub Action that generates sequential build numbers for workflows, storing them as Git refs without extra commits.
Build-number is a GitHub Action that generates sequential build numbers for CI/CD workflows. It automatically increments a counter each time it runs and stores the number as a Git tag, making it available to subsequent steps via environment variables or step outputs. This provides a simple way to track build versions without manual intervention or extra commits.
Developers and DevOps engineers using GitHub Actions for continuous integration who need persistent, incrementing build identifiers for versioning artifacts or tracking deployments.
It offers a lightweight, Git-native solution for build numbering that doesn't pollute commit history, supports multiple independent number sequences in one repo, and integrates seamlessly with GitHub's workflow system using standard tokens and outputs.
GitHub action for generating sequential build numbers.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Stores build numbers as lightweight Git tags (e.g., `build-number-42`) without adding commits, keeping repository history clean, as described in the README's philosophy.
Allows independent number sequences for multiple projects in one repository using the `prefix` parameter, enabling monorepo workflows, as shown in the 'Generating multiple independent build numbers' section.
Exposes build numbers via the environment variable $BUILD_NUMBER and step outputs like `steps.buildnumber.outputs.build_number`, seamlessly fitting into GitHub Actions workflows.
Supports setting initial numbers by manually creating Git tags (e.g., `build-number-500`), making it easy to transition from other build systems, as explained in the 'Setting the initial build number' section.
The action is no longer maintained as of January 2023, with development moved to a fork, posing risks for security, compatibility, and long-term support in evolving GitHub Actions environments.
GitHub now provides `GITHUB_RUN_NUMBER` and `GITHUB_RUN_ID` environment variables for unique run identifiers, reducing the need for external actions and avoiding dependency on unmaintained code.
Relies on creating and deleting Git tags for each build, which can lead to tag clutter or conflicts in repositories with extensive tagging, requiring manual cleanup or careful workflow design.
Only generates sequential integers without support for more sophisticated schemes like semantic versioning or branch-specific numbers, limiting its use for advanced release management.