agaric/forgejo_helpers
10
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update possibilities in README

Browse source
This commit is contained in:
benjamin melançon 2023-10-05 18:33:06 -04:00
parent 33b35a3566
commit 0af686e64c
1 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -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.