Skip to content
This repository has been archived by the owner on Aug 26, 2023. It is now read-only.

v0.0.5

Compare
Choose a tag to compare
@sealos-release-robot sealos-release-robot released this 30 Apr 12:32
· 38 commits to main since this release

labring: gh-rebot v0.0.5

We are excited to present to you the latest tool from labring: gh-rebot v0.0.5! Gh-rebot is a powerful automation tool designed specifically for GitHub repositories, with features such as handling issue and PR comments, automatic publishing, and auto-generating changelog files. In this article, we will provide a brief introduction to the main features of gh-rebot and how to obtain the corresponding Docker image.

Usage Instructions

gh-rebot is a powerful tool that can help you effortlessly handle issue and PR comments in your GitHub repositories while also automatically publishing and generating changelog files. To start using gh-rebot, you first need to download the precompiled binary file suitable for your operating system. You can find these files on our GitHub Releases page.

Installation

  1. Download the precompiled binary file suitable for your operating system.
  2. Unzip the binary file and place it in your PATH.

Usage

In the command line, run the following command to start gh-rebot:

gh-rebot [OPTIONS]

OPTIONS can include the following parameters:

  • --help: Display help information.
  • --version: Display the version information of gh-rebot.
  • Other optional parameters.

Docker Image

For added convenience, we also provide a Docker image for gh-rebot. You can obtain the image with the following command:

docker pull ghcr.io/labring/gh-rebot:v0.0.5

To run the gh-rebot Docker container, use the following command:

docker run --rm -it ghcr.io/labring/gh-rebot:v0.0.5 [OPTIONS]

Here, OPTIONS are the options you want to pass to gh-rebot.

Changelog

Other work

Full Changelog: v0.0.4...v0.0.5


Thank you for your interest and support in labring and gh-rebot! If you encounter any problems during use, please feel free to submit an issue in our GitHub repository. We will resolve your issue as soon as possible.