From e46dd63957551fc3d2bb7a66330b4a6a311921b5 Mon Sep 17 00:00:00 2001 From: Sebastian Kuzminsky Date: Sat, 26 Jul 2025 12:55:52 -0600 Subject: [PATCH] create new issue 131504dd52f3a9b358bfb4701e656fbe --- 131504dd52f3a9b358bfb4701e656fbe/description | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 131504dd52f3a9b358bfb4701e656fbe/description diff --git a/131504dd52f3a9b358bfb4701e656fbe/description b/131504dd52f3a9b358bfb4701e656fbe/description new file mode 100644 index 0000000..3c53fbd --- /dev/null +++ b/131504dd52f3a9b358bfb4701e656fbe/description @@ -0,0 +1,15 @@ +teach `ent sync` to scan `main` branch commits for special commands + +I'm thinking primarily of "Fixes: abc123" but maybe there are others? + +ent could be informed of the main branch name via +entomologist-data:config.toml, and use a special tag pointing at the +most recent commit in that branch that it has processed. When you run +`ent sync`, after it runs `git fetch` it could log the main branch from +its tagged commit to the just-fetched branch head, read all the commit +messages, and find and process all the ent commands. Then finally move +its tag to the new main branch head. + +This way you could put an ent command like "Fixes: abc123" in a bugfix +commit, and after you merge that branch to main, the next ent sync will +mark issue abc123 as done for you.