Change Details

We seem to occasionally get bug reports where the issue is resolved by restarting daemons. We should let users know when they are making edits that probably mean to restart the daemons at the time they make the edit. 1 example I know of from https://github.com/facebook/phabricator/issues/578 - Diffusion -> Repository Edit -> Change access key - edit form should have a "note" you'll need to restart daemons - final page after "save" should have a status element telling user to restart daemons I am sure there are more though... @epriestley, any come to mind?

Not all config changes require daemon restarts, but a bunch do. Give the user a banner suggesting they restart daemons.

We seem to occasionally get bug reports where the issue is resolved byNot all config changes require daemon restarting daemons.s, We should let users know when they are making edits that probably mean to restart the daemons at the time they make the edit. 1 example I know of from https://github.com/facebook/phabricator/issues/578 but a bunch do. Give the user a banner suggesting they restart daemons. - Diffusion -> Repository Edit -> Change access key - edit form should have a "note" you'll need to restart daemons - final page after "save" should have a status element telling user to restart daemons I am sure there are more though... @epriestley, any come to mind?