31 lines
1.4 KiB
Markdown
31 lines
1.4 KiB
Markdown
# Forgejo Helpers
|
|
|
|
Setup:
|
|
|
|
```bash
|
|
git clone https://git.agaric.com/agaric/forgejo_helpers.git
|
|
cd forgejo_helpers
|
|
cp .env.example .env
|
|
```
|
|
|
|
Set your instance URL there and your API token (with permission to read and write issues at least).
|
|
|
|
## Move issues
|
|
|
|
Currently this is the only script:
|
|
|
|
[`move_issue.py`](https://git.agaric.com/agaric/forgejo_helpers/src/branch/main/move_issue.py)
|
|
|
|
Use it by passing in the source owner, the source repository, the issue number, the destination owner, and the destination repository, like so:
|
|
|
|
```bash
|
|
python move_issue old-example-org old-example-repo 123 new-example-org new-example-repo
|
|
```
|
|
|
|
All five parameters are needed, even if it is within the same organization.
|
|
|
|
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.
|