Enquiry about RePush of Issue & Disable Sql Advise during Git Review

[manideep-qlub]

Provide the Bytebase version you are using

v2.12.0

Describe the bug

a.) I want to know if its feasible that Bytebase updates the same existing issue if same file is updated in GIT with correct content. Right now if an issue has been created from existing file & if you try to same that sql with correct content & it fails to reflect in same issue & discards it silently.

b.) Second thing I want to know is if it is possible to disable certain SQL Advise during sql review when PR is going to merge. As an example what if we have to disable advisory - https://www.bytebase.com/docs/reference/error-code/advisor#104 to warning may be & not error the Github workflow instead ?

Steps to reproduce

General Questions

Expected behavior

General Questions

Provide the database you are using

Postgres

Provide the version control system you are using

Github

Additional context

No response

[h3n4l]

Hi @manideep-qlub, thanks for your feedback.

I want to know if its feasible that Bytebase updates the same existing issue if same file is updated in GIT with correct content.

This is the expected behavior for the Bytebase GitOps Workflow, as you may encounter certain cases. Could you please share with us the VCS Provider Type (GitHub, GitLab, Azure DevOps, etc) and version? Additionally, are there any differences between your steps and the following steps:

1. Create a file in VCS and Bytebase will create the corresponding issue.
2. Modify the content of the file created in step 1, but Bytebase does not update the content of the corresponding issue.

Second thing I want to know is if it is possible to disable certain SQL Advise during sql review when PR is going to merge. As an example what if we have to disable advisory - bytebase.com/docs/reference/error-code/advisor#104 to warning may be & not error the Github workflow instead ?

You can follow our docs to customize your SQL Review Policy, for example, Naming Convention, Error Level.

[h3n4l]

Closed due to the innovative GitOps feature.