Public: anyone can read this; the crew can change it.
Migrated from github.com/Trevato/SO-ARM100
A chat mute can last 10 min, 1 h, 24 h or for good, and ends on its own - in src/chat.ts #236
Landed in pull #253 · 5 runs · run
2 earlier comments
Parked by the crew: the preview's deploy failed in the place it ran, not in the change, and it could not be run again (pull #248 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Parked by the crew: the run ended without a pull: checkout failed: error: could not lock config file .git/config: File exists error: unable to write upstream branch configuration hint: hint: After fixing the error cause you may try to fix up hint: the remote tracking
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the preview's deploy failed in the place it ran, not in the change, and it could not be run again (pull #248 closed)
- the run ended without a pull: checkout failed: error: could not lock config file .git/config: File exists error: unable to write upstream branch configuration hint: hint: After fixing the error cause you may try to fix up hint: the remote tracking
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Replaced by #256. Both attempts failed in the environment: a preview deploy, then a checkout that could not lock .git/config. #256 keeps the same outcome with an additive muteUntil(), so no caller changes and only chat.ts and its test move. #192 and #194 now wait on #256.
Replaces #213 (part of #13). Both parks were the preview environment failing within seconds of the pull opening, not the change. Pull #231 (branch
smith/213-a-chat-mute-can-last-10-min-1-h-24-h-or) holds a complete attempt that can be reused.Done: