Gitea Issue → Branch Action
Create a Git branch automatically from a Gitea issue, then attach that branch back to the issue via the Gitea REST API.
What it does
- Reads issue data from the workflow event.
- Maps issue labels → Git Flow prefix (
feature,bugfix,hotfix). - Creates a branch named
<prefix>/us-<ISSUE_NUMBER>fromorigin/develop(configurable). - Pushes the branch to the remote repository.
- Updates the issue so its “linked branch” points to the one it just created.
Environment variables
Only the following environment variables need to be set manually:
| Variable name | Required | Example value | Purpose |
|---|---|---|---|
GITEA_URL |
* | https://gitea.example.com |
Base URL of the Gitea instance |
GITEA_TOKEN |
* | xxxx… |
Personal access token with repo scope |
Label → prefix mapping
| Label | Prefix |
|---|---|
enhancement |
feature |
bug |
hotfix |
invalid |
bugfix |
| anything else | feature |
Quick start (Gitea Actions)
Example workflow YAML—act_runner builds the Dockerfile automatically:
- uses: gitea.ethumada.com/gitea/new-issue-branch@v1
env:
GITEA_URL: https://git.example.com
GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }}
Branch-naming rules
<prefix>/ticket-<ISSUE_NUMBER>
prefix= feature, bugfix, or hotfix (based on label table above)- Example:
feature/ticket-123,hotfix/ticket-7
Local development
# build and run the container locally
docker build -t gitea-issue-branch-action .
docker run --rm \
-e GITEA_URL=https://gitea.example.com \
-e GITEA_TOKEN=xxx \
gitea-issue-branch-action
Or use act to execute the full workflow.
📄 License
Distributed under the MIT License—see LICENSE for details.
Description
Languages
Go
91.3%
Dockerfile
8.7%