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
Perhaps over a certain number, the commit history is paginated meaning you don't get a string?
Note also that the stage where the error occurs is not the stage where it manifests: The error happens in the previous supposedly successful step
What is the expected behaviour?
The release notes compiler should exit with a non-zero code if it fails, so that the error is targeted to the right place
The release notes compiler should work with a long list of commits
To reproduce
Use either that particular PR, or take any repository with a long list of commits, look way back in the history, and check out a branch from there. Then make a PR from main into that branch and run the updater on it.
The text was updated successfully, but these errors were encountered:
Note: I've set this as a very low priority because it's unlikely to affect us often. It's more likely to hit people who use a trunk based development pattern (which I'm essentially doing in this particular case, due to a major overhaul).
Bug report
What is the current behaviour?
In this PR I have hundreds of commits.
I'm guessing that the number of commits is the problem, I'm not certain.
On running the
update-pull-request
action I get the following error:Perhaps over a certain number, the commit history is paginated meaning you don't get a string?
Note also that the stage where the error occurs is not the stage where it manifests: The error happens in the previous supposedly successful step
What is the expected behaviour?
To reproduce
Use either that particular PR, or take any repository with a long list of commits, look way back in the history, and check out a branch from there. Then make a PR from main into that branch and run the updater on it.
The text was updated successfully, but these errors were encountered: