you need to catch vulnerabilities "before" deployment because once it's in PROD with vulnerabilities, you would need to do a rollback. So, performing the tests in TEST environment is more appropriate and cause less headaches of having to rollback.
Status check on a PR of the feature branch. Once approved, merge to main.
Performing a check on the main branch means that it's already been approved and failed the status check after approval.
when you configure the status check in the policies of the main branch it means it is a requirement to complete pull requests to main. not that it checks the main after merge.
I would say option A Option B could work but is less ideal because it's applied to the main branch, and security validation should generally be enforced earlier in the development process (e.g., on the feature/development branches) to catch issues before they reach the main branch.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Dankho
2 days, 21 hours agoyaguitoEC
1 week, 6 days agoZangi
1 week, 6 days agoMrAZ105
1 month, 1 week agoUrbanRellik
1 month, 2 weeks agoDaveVentura
1 week, 1 day agoMrAZ105
2 months agoUrbanRellik
1 month, 2 weeks ago