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
It was discussed in recent QA and catapult meeting that everything which is relevant to scf should be in branch and master should only contain kubecf related code. This will simplify catapult to some extent and help us with feature enhancements.
The text was updated successfully, but these errors were encountered:
I'm removing the priority critical label; it can wait until we are not breaking the pipelines, we have unit & integration test coverages and we are not endlessly backporting changes on the last 4 days (eg: #128).
If you feel it's priority critical, then I suggest you open a PR with the changes + unit & integration tests, links to personal versions/forks of runs of the ~12 pipelines that prove the changes don't break them.
It was discussed in recent QA and catapult meeting that everything which is relevant to scf should be in branch and master should only contain kubecf related code. This will simplify catapult to some extent and help us with feature enhancements.
The text was updated successfully, but these errors were encountered: