-
Notifications
You must be signed in to change notification settings - Fork 663
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enquiry about RePush of Issue & Disable Sql Advise during Git Review #10455
Comments
Hi @manideep-qlub, thanks for your feedback.
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:
You can follow our docs to customize your SQL Review Policy, for example, Naming Convention, Error Level. |
Closed due to the innovative GitOps feature. |
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
The text was updated successfully, but these errors were encountered: