You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the body length of a merge request is too long, the creation on GitHub fails.
There are two issues with this:
the PR is never created
the migration continues potential leading to an inconsistent numbering of PRs compared to MRs (if this is needed)
I suggest to detect this issue and stop the process giving the user the ability to shorten the body length.
In our case this happened for a dependency update of node which includes the release notes. It was a change over several versions so there were lots of changes. node includes (or used to?) all commits of a release.
The text was updated successfully, but these errors were encountered:
When the body length of a merge request is too long, the creation on GitHub fails.
There are two issues with this:
I suggest to detect this issue and stop the process giving the user the ability to shorten the body length.
In our case this happened for a dependency update of node which includes the release notes. It was a change over several versions so there were lots of changes. node includes (or used to?) all commits of a release.
The text was updated successfully, but these errors were encountered: