You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
In my case `release-1.0.2` is my first release, when running the `git log main release-1.0.2.. --all --no-merges --decorate --pretty="format:%D%n - %s"` command from my PC, I get the entire log, and when running from the pipeline I get an error
+ git log main release-1.0.2.. --all --no-merges --decorate --pretty="format:%D%n - %s" > changelog.txt
fatal: ambiguous argument 'release-1.0.2..': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
When a Pipelines build runs, the behavior of the git clone command is determined by the type of pipeline and the way it was triggered. For example, for a branch pipeline that is triggered automatically only that branch is cloned with a default depth of 50. It is possible to specify full depth for a step and then check out another branch if needed:
I can give you advice specific to your use case if you let me know the following: