[x] Log in with OTP but supply invalid OTP, verify an error message shows as "OTP is not valid"
[x] Submit the same invalid OTP multiple times till the message becomes "Max number of attempts reached", subsequent attempt will keep showing that same message
Modify the production form to be similar to the one in staging. Concretely, add a dropdown with the
title
Repair mode
description:
Select 'Only lock repo' if you want to do manual repairs directly on Github.
Select 'Repair without acquiring lock' if you want to sync the changes from Github onto EFS and you have already submitted this form to lock the repo.
Select 'Repair with acquiring lock' if you want to just want to repair the repo as is without any modification.
options:
Only lock repo
Repair without acquiring lock
Repair with acquiring lock
It should match what you see here:
This needs to be released prior/in the same release as #1313. Once this is live, inform the isomer channel about the newer flow.
New
#1328#1327#1326#1325#1323#1295#1311#1322Tests
feat(repair): add locking functionailty
#1327ISOM-951: Better cloudmersive logging
#1323Fix + Refactor: improve verify otp flows
#1295@dcshzjDeploy Notes
feat(repair): add locking functionailty
#1327@dcshzjModify the production form to be similar to the one in staging. Concretely, add a dropdown with the
title
Repair mode
description:
Select 'Only lock repo' if you want to do manual repairs directly on Github. Select 'Repair without acquiring lock' if you want to sync the changes from Github onto EFS and you have already submitted this form to lock the repo. Select 'Repair with acquiring lock' if you want to just want to repair the repo as is without any modification.
options:
Only lock repo Repair without acquiring lock Repair with acquiring lock
It should match what you see here:
This needs to be released prior/in the same release as #1313. Once this is live, inform the isomer channel about the newer flow.
Full Changelog: https://github.com/isomerpages/isomercms-backend/compare/v0.81.1..v0.82.0