gitlab_tagger
| Crates.io | gitlab_tagger |
| lib.rs | gitlab_tagger |
| version | 0.1.3 |
| source | src |
| created_at | 2023-10-16 08:50:00.073324 |
| updated_at | 2023-11-23 04:36:17.942348 |
| description | Simple crate to create tag using gitlab api |
| homepage | https://gitlab.com/yessetmurat/gitlab_tagger.git |
| repository | |
| max_upload_size | |
| id | 1004572 |
| size | 42,059 |
Yesset Murat (yessetmurat)
documentation
README
Introduction
This project presents a tool for creating GitLab tags using the GitLab API. It's designed to automate the tagging process in GitLab repositories, making version control more efficient.
Requirements
- GitLab account with appropriate permissions.
- Private access token for GitLab API authentication.
Installation
To install gitlab_tagger, use the following Cargo command:
cargo install gitlab_tagger
Usage
The tool requires the following arguments:
- Server URL (
-s): The URL of your GitLab server. - Project ID (
-i): The ID of your GitLab project. - Private Access Token (
-p): Your GitLab private access token for API interaction. - Branch (
-b): The branch for which to create the tag. - Previous Tag (
-t): The latest tag in your project. - Commit Message (
-c): The commit message should start with 'major', 'minor', or 'patch', followed by a colon and a short description.
Example of Usage
tagger -s "${CI_SERVER_URL}" -i "${CI_PROJECT_ID}" -p "${PRIVATE_TOKEN}" -b "${CI_DEFAULT_BRANCH}" -t "$(git describe --tags --abbrev=0)" -c "${CI_COMMIT_TITLE}"
How it Works
The script interacts with the GitLab API using the provided arguments to create a new tag. The new tag version is determined based on the previous tag and the change type (major, minor, patch) indicated in the commit message.
Contributing
Contributions are welcome. Fork the repository, make your changes, and submit a pull request.
License
This project is licensed under the MIT License. See the LICENSE file for more details.