bcb81ef99f
Some checks failed
Tests / Build and Push CICD Base Image (pull_request) Failing after 31m40s
Tests / Build and Push CICD Complete Image (pull_request) Has been skipped
Tests / End of File Check (pull_request) Has been skipped
Tests / Trailing Whitespace Check (pull_request) Has been skipped
Tests / YAML Syntax Check (pull_request) Has been skipped
Tests / TOML Syntax Check (pull_request) Has been skipped
Tests / Mixed Line Ending Check (pull_request) Has been skipped
Tests / TOML Formatting Check (pull_request) Has been skipped
Tests / Ruff Linting (pull_request) Has been skipped
Tests / Ruff Format Check (pull_request) Has been skipped
Tests / Pyright Type Check (pull_request) Has been skipped
Tests / Darglint Docstring Check (pull_request) Has been skipped
Tests / No Docstring Types Check (pull_request) Has been skipped
Tests / ESLint Check (pull_request) Has been skipped
Tests / Prettier Format Check (pull_request) Has been skipped
Tests / Backend Tests (pull_request) Has been skipped
Tests / TypeScript Type Check (pull_request) Has been skipped
Tests / Frontend Tests (pull_request) Has been skipped
Tests / Backend Doctests (pull_request) Has been skipped
Tests / TSDoc Lint Check (pull_request) Has been skipped
Tests / End-to-End Tests (pull_request) Has been skipped
Tests / Integration Tests (pull_request) Has been skipped
Signed-off-by: copilotcoder <copilotcoder@darkhelm.org>
810 B
810 B
Issue Tracker
This repository uses Gitea issues as the canonical issue tracker.
Platform
- Host: dogar.darkhelm.org
- Repository: DarkHelm.org/plex-playlist
- Tracker mode: GitHub-style issue workflow on Gitea
How skills should use this tracker
- Read open and closed issues in this repository as the source of truth.
- Create new issues in this repository when a skill generates implementation work.
- Update existing issues with status, notes, and cross-references to branches and pull requests.
- Reference issue IDs in branch names and PR descriptions using the PP- prefix convention.
Operational notes
- Prefer repository issues over local scratch files for planning and tracking.
- If automation tooling expects GitHub semantics, treat Gitea issues as equivalent for workflow purposes.