Add support for renaming an existing repository · Pull Request !27 · openEuler/ci-bot

Fix #I18ZB8 .

# Background
Previously, to change the name of a repository, we have to define an new repository item and remove the old one in `src-openeuler.yaml` or `openeuler.yaml`. But that will completely remove the old repository and create an new empty new one, which would cause all the existing issues and PRs get lost. It's definitely unexpected and a critical bug. Please check out #I18ZB8 for more details.

# How to implement
This PR is going to introduce a new property `rename_from` for the repository definition. This property will be capable of supporting the renaming operation on an existing repository, which could also keep all the issues and PRs unchanged. While it should noted that `rename_from` is not declarative but imperative cause it will take effect only for once and not stored in DB. So if we remove it from repository definition after renaming operation has been finished, nothing will happen.

Since renaming will also create a new repository, so the implementation is trying to distinguish the renaming or creating operation within the single function `addRepository`.

# The example
Please let me take a real case for example, the relevant PR is avaliable at https://gitee.com/openeuler/community/pulls/128. iSulad team wants to change the names of three packages:
- iSulad-kit ===> iSulad-img
- iSulad-lxcfs-toolkit ===> lxcfs-tools
- iSulad-tools ===> syscontainer-tools

Before the rename operation is supported, the diff was as the following, which would completely remove the old repository and create a new empty one with the new name, causing loss of all the existing issues and PRs.

```diff
- - name: iSulad-kit
+ - name: iSulad-img
    description: ""
- - name: iSulad-lxcfs-toolkit
+ - name: lxcfs-toolkit
    description: ""
- - name: iSulad-tools
+ - name: syscontainer-tools
    description: ""
```

While the diff would be like this, after renaming repository is supported. This could make use of the newly supported renaming-repository Gitee OpenAPI to keep all the issues and PRs.

```diff
- - name: iSulad-kit
+ - name: iSulad-img
    description: ""
+   rename_from: iSulad-kit
- - name: iSulad-lxcfs-toolkit
+ - name: lxcfs-toolkit
    description: ""
+   rename_from: iSulad-lxcfs-toolkit
- - name: iSulad-tools
+ - name: syscontainer-tools
    description: ""
+   rename_from: iSulad-tools
```

# How I tested this PR

1. Set the giteeToken and database related parameters in `config.yaml` to feasible values;
2. Fork `openeuler/community` project to openkylin organization which I have full access rights;
3. Fulfill the `watchProjectFiles` section in my local `config.yaml` with the ones I created in step 2;
4. Add/Delete the `rename_from` property of the repository definitions in `repository/openeuler.yaml` under `openkylin/community` project and push into Gitee;
5. Manually get the sha of `repository/openeuler.yaml` and update to my local mysql;
6. Check if renaming operation, as well as creating operation, are successfully performed;

Any feedback is welcome. Thanks.

openEuler/ci-bot .gitee-modal { width: 500px !important; }

搜索帮助

openEuler/ci-bot