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 using "commitDepth: 1", it seems that instead of getting the 1 latest commit, I get the first one.
Expected behaviour:
"commitDepth: 1" gives me: "This is the last commit"
Actual behaviour:
"commitDepth: 1" gives me: "This is the first commit"
Looking over this PR (https://github.com/wagoid/commitlint-github-action/pull/595/files) where the feature was implemented, it appears that it simply slices an array of commits (from, to), but my best guess is that the order of the original array was misunderstood to already be latest to earliest, rather than earliest to latest.
The text was updated successfully, but these errors were encountered:
Given a theoretical list of commits:
When using "commitDepth: 1", it seems that instead of getting the 1 latest commit, I get the first one.
Expected behaviour:
"commitDepth: 1" gives me: "This is the last commit"
Actual behaviour:
"commitDepth: 1" gives me: "This is the first commit"
Looking over this PR (https://github.com/wagoid/commitlint-github-action/pull/595/files) where the feature was implemented, it appears that it simply slices an array of commits (from, to), but my best guess is that the order of the original array was misunderstood to already be latest to earliest, rather than earliest to latest.
The text was updated successfully, but these errors were encountered: