build: establish Tree Feller project

This commit is contained in:
dmg
2026-08-11 17:10:33 -04:00
parent de27d6519e
commit 39fb3cfc57
15 changed files with 664 additions and 7 deletions
@@ -2,7 +2,7 @@
type: User Story
title: "US-009: Build and release Tree Feller"
description: Give maintainers repeatable Spigot builds, automated verification, and versioned Gitea releases.
status: backlog
status: in-progress
---
# US-009: Build and release Tree Feller
@@ -11,17 +11,17 @@ As a **plugin maintainer**, I want automated builds and releases modeled on `spi
## Acceptance criteria
- [ ] The Gradle project compiles against Spigot API `26.2-R0.1-SNAPSHOT` using a Java 17 toolchain.
- [ ] Compiler lint warnings fail the build.
- [ ] Automated JUnit 5 tests run as part of the Gradle check lifecycle.
- [x] The Gradle project compiles against Spigot API `26.2-R0.1-SNAPSHOT` using a Java 17 toolchain.
- [x] Compiler lint warnings fail the build.
- [x] Automated JUnit 5 tests run as part of the Gradle check lifecycle.
- [ ] Pushes and pull requests build and test Tree Feller in Gitea Actions.
- [ ] Pull requests validate conventional commit messages.
- [ ] CI stores a development Tree Feller JAR as a workflow artifact.
- [ ] Main-branch conventional commits drive semantic versioning.
- [ ] A successful release builds a versioned Tree Feller JAR and attaches it to the corresponding Gitea release.
- [ ] Build files, Gradle wrapper, workflows, release behavior, and Java dependency versions follow `../spigot-getgud/` where applicable while using Tree Feller names and identifiers.
- [ ] Plugin metadata declares the player and administrative command trees with separate permissions.
- [ ] The approved user-story bundle is committed before implementation begins.
- [x] Build files, Gradle wrapper, workflows, release behavior, and Java dependency versions follow `../spigot-getgud/` where applicable while using Tree Feller names and identifiers.
- [x] Plugin metadata declares the player and administrative command trees with separate permissions.
- [x] The approved user-story bundle is committed before implementation begins.
- [ ] Subsequent implementation follows test-driven development where practical and keeps story statuses and acceptance criteria synchronized with verified behavior.
- [ ] No remote push is performed until the maintainer confirms that the Gitea repository and release token secret are ready.