CHAAAAAAAAAAAOOOOOOOOOSSSSSSS #101
Conversation
|
|
||
| ChaosBot is a social coding experiment to see what happens when the absolute | ||
| direction of a software project is turned over to the open source community. | ||
| ### _CHAAAAAAAAAAAOOOOOOOOOSSSSSSS_ |
There was a problem hiding this comment.
Shouldn't be italics and all-caps
There was a problem hiding this comment.
Or you know, should be italics and all caps twice. Like, twice as upper case characters.
|
|
||
| ChaosBot is a social coding experiment to see what happens when the absolute | ||
| direction of a software project is turned over to the open source community. | ||
| ### _CHAAAAAAAAAAAOOOOOOOOOSSSSSSS_ | ||
|
|
||
|  |
|
|
||
|  | ||
|
|
||
| ## How it works |
There was a problem hiding this comment.
How are people going to know how to use the bot if there are no instructions.
| Chaosbot has died 4 times. This counter is incremented whenever the trunk breaks | ||
| and the server must be restarted manually. | ||
|
|
||
| ## Server details |
There was a problem hiding this comment.
How are users going to know server parameters
|
👎 |
|
(N) |
|
👎 |
|
Why hasn't this been closed yet? :| |
|
This can't be merged or closed by votes because there are still conflicts which need to be resolved. It will eventually be closed for being stale. Right now, that code looks at the last push to the originating repo, which was 10 hours ago. With the current code, it needs 24 hours before it will be closed as stale. #271 will instead have Chaos look at the last push to this particular PR instead. |
|
🙅 This PR has merge conflicts, and hasn't been touched in 57 hours. Closing. Open a new PR with the merge conflicts fixed to restart voting. |
No description provided.