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
Currently, if git commit fails for what-ever reason, this goes unnoticed by the users. Their change will only not appears on GitHub, and on next reload, disappear.
Fix this by capturing such events, and put the wiki in read-only till an operator fixed it.
The text was updated successfully, but these errors were encountered:
Changed my mind: we are simply going to terminate the process if such unexpected exception happens.
In normal production workflows, this should cause the start of a new process, cleaning everything back up (but the commit will be lost).
In development workflows, it makes it more clear what happened immediately.
Currently, if
git commit
fails for what-ever reason, this goes unnoticed by the users. Their change will only not appears on GitHub, and on next reload, disappear.Fix this by capturing such events, and put the wiki in read-only till an operator fixed it.
The text was updated successfully, but these errors were encountered: