How to Ignore some files in bitbucket-chatgpt-codereview or not fail pipeline.

[Sergey Mokhov]

Hi there!

I'm trying to use the chatgpt pr review pipe and it fails with "too many tokens in your message (over 128000)" whenever I edit a large file. The file is an sql dump of test data and generally contains nothing to review. The changes in PR are +350/-250 across 20 files, and 90% of the line changes are in that file.

Is there a way to add an ignore list to avoid situations like this?

Also, would be really nice to be able not to fail pipeline if this pipe fails. It has to be in the "PR" pipe, so when it fails there is no way to merge and it blocks the workflow. Very disruptive for no reason.

A

[Patrik S · Accepted solution]

Hello @Sergey Mokhov ,

and welcome to the Community!

It's indeed not currently possible to ignore particular files from the chat-gpt review. I've gone ahead and raised a feature request with our development team suggesting the addition on this functionality, which you can check on the following link:

• https://jira.atlassian.com/browse/BCLOUD-23596

I would suggest you to add your vote there, since this helps both developers and product managers to understand the interest. Also, make sure you add yourself as a watcher in case you want to receive first-hand updates from that ticket. Please note that all features are implemented with this policy in mind.

As for not fail the pipeline when the pipe fails, you can achieve this behavior by leaving the pipe on it's own step and configuring that step to ignore failures, as the below example:

    - step:
        name: 'Review Step - ignore fail '
        on-fail:
          strategy: ignore
        script:
          - pipe: atlassian/bitbucket-chatgpt-codereview:0.2.0 
               variables:
                  <PIPE VARIABLES>

Fore more details on how the on-fail strategies work, the following documentation might be of help:

• Step Options - On-fail 

Thank you, @Sergey Mokhov !

Patrik S

[Sergey Mokhov]

Hi Patrik, thank you for your assistance, I will try the workaround.