Upgrade verify-safe-to-test-label to v2#2204
Conversation
|
Visit the preview URL for this PR (updated for commit f59f20f): https://sharezone-console-dev--pr2204-upgrade-verify-safe-z1i7rv1s.web.app (expires Wed, 04 Mar 2026 18:34:41 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 471536afe3f6ec4895d9ea75513730b515d17eb6 |
|
Visit the preview URL for this PR (updated for commit f59f20f): https://sharezone-website-dev--pr2204-upgrade-verify-safe-knqbn9ud.web.app (expires Wed, 04 Mar 2026 18:34:44 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 372b0431a96247f908d9a97d5d865de1c8b3b04e |
|
Visit the preview URL for this PR (updated for commit f59f20f): https://sharezone-test--pr2204-upgrade-verify-safe-0v7cvocw.web.app (expires Wed, 04 Mar 2026 18:35:19 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 4cb3ae61e1e018abfd9841fd3239f5b49ccc034b |
|
Visit the preview URL for this PR (updated for commit f59f20f): https://sharezone-docs-dev--pr2204-upgrade-verify-safe-7nwnrpni.web.app (expires Wed, 04 Mar 2026 18:33:42 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 4df6a337bd98af9195d10af6d0ed29fd86a3b756 |
|
/gemini review |
With v2 of the verify-safe-to-test-label there is no need for a second remove-safe-to-test-label GitHub Action. With the
require-reapprovalparameter of the verify-safe-to-test-label immediately removes the "safe to test" label after it verified it.With this PR, we now always first check the "safe to test" label, remove it, run the "changes" job and then the actual job: