From 0af686e64c55d0a581066ebff60b73533f1f6631 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?benjamin=20melan=C3=A7on?= Date: Thu, 5 Oct 2023 18:33:06 -0400 Subject: [PATCH] Update possibilities in README --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 2ffe826..46301a9 100644 --- a/README.md +++ b/README.md @@ -24,4 +24,8 @@ python move_issue old-example-org old-example-repo 123 new-example-org new-examp All five parameters are needed, even if it is within the same organization. -It would not be difficult to change it so these could be environment variables so that only the issue need to be passed in, and in would not be hard to allow passing in a list of issues, but this has not been done yet. +It would be easy to change it so these could be environment variables so that only the issue number needs to be passed in, and it would be pretty easy to allow passing in a list of issues, but this has not been done yet. + +It would not be too hard to allow separate source and destination instances and auth tokens, either, which could give this script a reason for being even after [#1280 - [FEAT] transfer issues to another repo - forgejo](https://codeberg.org/forgejo/forgejo/issues/1280) lands! + +Although it is probably best to prioritize bulk export and import of issues even over moving single issues, as that tests the API the best and covers the broadest use cases.