Timeline for Should minified CSS be stored in Git?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 20, 2017 at 19:38 | comment | added | ptyx | @ButtleButkus ...also not so much a problem in many devops scenario when source == deliverable, e.g. puppet or configuration. | |
| Apr 20, 2017 at 17:54 | comment | added | ptyx | @ButtleButkus I don't have a lot of expertise on the devops case. What I've seen is git used as a (very convenient and flexible) transport/release/deployment mechanism, rather than purely as source control. Unless the 'source' git and the 'delivery' git are separate (separate repos or separate branches), this means you have to compromise the source->build->deliverable chain somewhat - e.g you'll end up with production having source code and extra branches lying around, and development with unused binary products. It's a pragmatic compromise, but I prefer separating concerns when I can. | |
| Apr 19, 2017 at 6:26 | comment | added | Buttle Butkus | What about Jonathan Eunice's "DevOps" reasoning? I've heard of git hooks and I wonder if they could take care of automated building whenever source is updated. | |
| Sep 11, 2016 at 8:03 | audit | First posts | |||
| Sep 11, 2016 at 8:03 | |||||
| Aug 31, 2016 at 16:45 | comment | added | ptyx | @R you can compromise - but it's just that. And in the case of CSS minification, I don't think the tools qualify as 'heavyweight' or 'slow' or 'inconvenient'. Also, there are alternative dependency injection mechanisms (maven, ivy...) that work well and don't require you to put generated code in your source control. | |
| Aug 31, 2016 at 3:48 | comment | added | Kevin | @R..: Ideally, you maintain a separate artifact repository for those things, but reality is rarely ideal. | |
| Aug 31, 2016 at 2:34 | comment | added | R.. GitHub STOP HELPING ICE | This principle is not always true. If you have files that are generated with heavyweight tools you can't expect a user to have, it may make sense to put the generated files in git. Many people even put generated autoconf configure scripts in git for this reason. | |
| Aug 30, 2016 at 21:15 | comment | added | candied_orange | Think of generated code the way you think of executable code. | |
| Aug 30, 2016 at 20:55 | vote | accept | Connor Gurney | ||
| Aug 30, 2016 at 23:07 | |||||
| Aug 30, 2016 at 20:53 | history | edited | ptyx | CC BY-SA 3.0 | explaining why... |
| Aug 30, 2016 at 20:50 | history | answered | ptyx | CC BY-SA 3.0 |