Timeline for Would it be a bad idea to periodically run code formatters on a repository?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Apr 12, 2017 at 16:41 | history | suggested | donjuedo | CC BY-SA 3.0 | minor clean up |
| Apr 12, 2017 at 14:08 | review | Suggested edits | |||
| S Apr 12, 2017 at 16:41 | |||||
| Apr 12, 2017 at 13:47 | comment | added | jwenting | @StarWeaver why do you think I still remember that environment 14 years later ;) | |
| Apr 12, 2017 at 8:00 | comment | added | Weaver | That's … I'm going to go have nightmares now >.> | |
| Apr 12, 2017 at 7:40 | comment | added | jwenting | @StarWeaver you'd think. But I've worked in places where the "code repository" was a shielded directory only accessible by a piece of software running under its own user account, no version control at all except a weekly backup of the directory under a timestamped directory name. | |
| Apr 12, 2017 at 7:35 | comment | added | Weaver | I think if he's talking about having a bot check things in and out of a repository, VCS is a given? | |
| Apr 12, 2017 at 7:13 | history | answered | jwenting | CC BY-SA 3.0 |