## @Ta180m workflow

The [repository](https://gitea.com/Ta180m/gitea) has several branches:

* [main](https://gitea.com/Ta180m/gitea/src/branch/main) is a duplicate of Gitea main.
* [dev](https://gitea.com/Ta180m/gitea/src/branch/dev) is where development happens and is deployed for testing at https://git.exozy.me/. Commits to the dev branch are usually cherry-picked to the feature branches as needed.
* [feature-activitypub](https://gitea.com/Ta180m/gitea/src/branch/feature-activitypub) corresponds to [PR #19133](https://github.com/go-gitea/gitea/pull/19133).
* [feature-manual-inbox-outbox](https://gitea.com/Ta180m/gitea/src/branch/feature-manual-inbox-outbox) contains an experimental inbox/outbox implementation. I will make a new branch with cleaner code for my upcoming inbox/outbox Gitea PR.

All the other branches mostly contain some experimental code and aren't important.

For testing, I run `TAGS="bindata" make && sudo systemctl stop gitea && sudo cp gitea /usr/bin/gitea && sudo systemctl start gitea` on the `dev` branch to deploy to https://git.exozy.me/ It's not the cleanest or fastest solution but it works.