hello,
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
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>...]'
Hi Maoz,
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:
Kind regards,
Theodora
thanks so much for your response, release-1.0.2 is a tag on a commit from the main branch.
The pipeline runs on a branch definition (main).
pipelines:
branches:
main: .....
In my case adding `depth: full
` solved the issue.
clone:
depth: full
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's good to hear Maoz, thank you for the update. Please feel free to reach out if you ever need anything else!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.