Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration of releases fails if release body is null #188

Open
privet-kitty opened this issue Aug 30, 2023 · 0 comments
Open

Migration of releases fails if release body is null #188

privet-kitty opened this issue Aug 30, 2023 · 0 comments

Comments

@privet-kitty
Copy link

Hi. Thanks for maintaining this awesome tool.

Migration of GitLab releases fails if description field is null. This is because GitLab assumes null for an optional field but node-gitlab-2-github doesn't

Tracing back the cause, as described in the issue above, it was due to the type definition of gitbeaker's Release.description, which node-gitlab-2-github just trusts it. I asked gitbeaker's author to fix it and he has already fixed it. Therefore, the problem will be resolved if node-gitlab-2-github uses gitbeaker 39.7.0, which would (unfortunately) need some other changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant