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
We should disable tide and provide information about it to ALL teams upfront. We should provide information what should be used instead with the link to the Github documentation.
Reasons
Removal of Prow.
Acceptance Criteria
[ ] Teams are notified upfront about disablement of the Tide
[ ] Teams are notified what they should use instead of Tide
[ ] Prow tide component is disabled for ALL teams
If you are planning to remove Tide, there is a small problem with GitHub actions, because if someone approves PR before passing all of the checks, then PR is merged without checks.
Adding workflows to branch protection on Github doesn't make sense, because paths (old run_if_change) is not working, when I want to change something in the Busola backend, I don't want to trigger the build of the web image.
If it will be possible to create one Github workflow to have one check to add in branch protection in repo settings which will be checking if all checks passed, I'd appreciate it.
Goats have some potential solutions: kyma-project/istio@4f3ee64
Description
We should disable tide and provide information about it to ALL teams upfront. We should provide information what should be used instead with the link to the Github documentation.
Reasons
Removal of Prow.
Acceptance Criteria
[ ] Teams are notified upfront about disablement of the Tide
[ ] Teams are notified what they should use instead of Tide
[ ] Prow tide component is disabled for ALL teams
Attachments
#12139
The text was updated successfully, but these errors were encountered: