excludePaths features does not work when push is done by bot

[Stevedan Ogochukwu Omodolor Omodia]

When I change the content of the version folder manually, the excludepath features works. The problem is when this is done by a bitbucket bot. I have a bibtucket bot that when I push to develop, it updates the version on the repo. The issue is that in this case the pipeline runs. Why is this the case?

  branches:

    'develop':

      - stage:

          name: Development stage

          condition:

            changesets:

              excludePaths:

                - "version/**"

          steps:

            - step: *bump_dev_version

[Syahrul]

Hey @Stevedan Ogochukwu Omodolor Omodia 

Sorry! I don't fully understand the issue here. Could you please provide more context?

For example, could you explain what you mean by 'Bitbucket bot'? Is this a user account acting as a "bot" or something different? Also, when you mention this "bot" committing to the develop branch to update versions and trigger the pipeline, could you clarify that?

I’d love to better understand your current workflow, your expected workflow, and what you see as the output so that I can advise you better.

Regards,
Syahrul

[Stevedan Ogochukwu Omodolor Omodia]

The bot is a user account I use for git committing automatically to my repo. 

My current workflow is as follows:

I have a develop branch. In order to merge to development branch, you need to PR, when a pull request is merged, I update the development version folder. This is done with the bot user account that git commits the new version to the development file. 

I use the excludepath to prevent running the pipeline when there are changes in the version folder. 

The problem. 

I tested the excludepath behavior and notices that i t works when for example I have a branch and I changed the version folder with a commit. The issue lies when this is done by the bot automatically as I explained before. It does not work. The pipeline still runs. 

This is what I do for more context

######## bump the version ########
git reset --hard HEAD # Reset all changes
git pull --rebase # Ensure latest code
mkdir -p version

***** Version update****

git add version
git commit -m "Version update ${current_version}"
git push

[Syahrul]

Hey @Stevedan Ogochukwu Omodolor Omodia 

Got it! If that's the situation, please go ahead and submit a support ticket on our Support portal so we can take a closer look at this. We’ll want to check your pipeline build and commit details. When you do, kindly include your pipeline URL where it was triggered when the bot account made the commit.

Regards,
Syahrul