Added Github Actions

[matejstastny]

THT-416

This branch sets up the full CI/CD and code quality pipeline for the repo, covering C++, Python, shell scripts, documentation, and PR hygiene.

Clang Format Check (.github/workflows/clang-format.yml)

Runs on any push or PR that touches C/C++ source files (.cpp, .cc, .cxx, .c, .h, .hpp, .hxx) or the .clang-format config itself.

Python Lint & Format Check (.github/workflows/python-lint.yml)

Runs on any push or PR touching .py files or pyproject.toml.

Uses Ruff to enforce linting.

Note

Formatter configs are configured in #5, this is just CI

Shell Format Check (.github/workflows/shell-format.yml)

Runs on any push or PR touching .sh or .bashrc files.

Uses shfmt to check that shell scripts are consistently formatted.

Deploy GitHub Pages (.github/workflows/pages.yml)

Runs on push to main when files under docs/ change, or manually via workflow_dispatch.

Builds the Astro documentation site (docs/) with Node 22 and deploys it to GitHub Pages.

Stale PR & Issue Bot (.github/workflows/stale.yml)

Runs every Monday at 9am UTC, or manually via workflow_dispatch.

After 14 days of no activity, adds a stale label and posts a warning comment. After 7 more days of silence, closes the issue or PR. Draft PRs and anything labelled pinned, security, or in-progress are exempt.

Source folder scaffolding

Added src-autonomy/ and src-platform/ just to make CI not fail. Only have a .gitkeep.

TODO BEFORE MERGE

• A TRICKFIREBOT_PRIVATE_KEY needs to be added to repo action secrets
• Github pages deployment from CI needs to be turned on

[alexrsing]

Looks good. I do think we should include testing frameworks into the ci pipeline, which should also be enforced throughout development of this repo. Frameworks like pytest and GTest, unless someone has other suggestions, would be good.

[matejstastny]

That is a good idea, I am going to be entirely honest, I have zero expirience doing/writing tests, I have never done it before, but we should set it as a goal in the future.

[CPrutean]

I agree with alex i think adding tests into CI makes the overall repo experience a little better we can immediately tell what PR's are off or what pushes cause issues.