You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to this GitLab issue, when a branch is deleted, GitLab sends a specially populated push event. Currently CxFlow does not handle this. I have not tested it but I imagine that it behaves as it does for BitBucket server (see issue #644).
Proposed solution
Implement the same logic as in GitHub to not scan delete push events and to delete SAST projects for the branch.
Additional details
Here is the sample push payload, associated with branch deletion, from the issue linked to above. Properties with values specific to a branch deletion push event are marked with //important.
Describe the problem
According to this GitLab issue, when a branch is deleted, GitLab sends a specially populated push event. Currently CxFlow does not handle this. I have not tested it but I imagine that it behaves as it does for BitBucket server (see issue #644).
Proposed solution
Implement the same logic as in GitHub to not scan delete push events and to delete SAST projects for the branch.
Additional details
Here is the sample push payload, associated with branch deletion, from the issue linked to above. Properties with values specific to a branch deletion push event are marked with
//important
.The text was updated successfully, but these errors were encountered: