From bb8615e3de3bf38a2d240ff1b001f1ad759d4c19 Mon Sep 17 00:00:00 2001
From: Anthony Wang
Date: Thu, 28 Apr 2022 21:15:51 +0800
Subject: Update 'Development'

---
 Development.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)
 create mode 100644 Development.md

diff --git a/Development.md b/Development.md
new file mode 100644
index 0000000..0ba8332
--- /dev/null
+++ b/Development.md
@@ -0,0 +1,12 @@
+## @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.
-- 
cgit v1.2.3-70-g09d2