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
Description of issue or feature request
One of the very first step in a merge commit is to compare the PR and master branch to determine the changes (i.e., added/deleted/modified files). le-git-imate uses different APIs to make the comparison on GitHub and GitLab.
However, those API may fail to function correctly if the number of commits in the PR exceeds a limit. On GitHub you can use the CompareBranch API to compare up to 250 commits. And if the number of changed files in a PR goes over 300, we can't simply use one API to list the files.
On GitLab, a diff API between two branches/commits may completely collapse if:
Support large merge commits which needs to
-- first know all limitations we have when we use GitHub API to compare branches.
-- second use alternative solutions like what is suggested by GitHub.
The text was updated successfully, but these errors were encountered:
Description of issue or feature request
One of the very first step in a merge commit is to compare the PR and master branch to determine the changes (i.e., added/deleted/modified files). le-git-imate uses different APIs to make the comparison on GitHub and GitLab.
However, those API may fail to function correctly if the number of commits in the PR exceeds a limit. On GitHub you can use the
CompareBranch API
to compare up to 250 commits. And if the number of changed files in a PR goes over 300, we can't simply use one API to list the files.On GitLab, a diff API between two branches/commits may completely collapse if:
This issue could be address with #11.
Current behavior
Expected behavior
-- first know all limitations we have when we use GitHub API to compare branches.
-- second use alternative solutions like what is suggested by GitHub.
The text was updated successfully, but these errors were encountered: