silverstripe-framework/docs/en
Ingo Schommer 1ae2709cca Use "composer update" in contrib docs
The "repositories" key makes "composer update" ridiculously slow with the amount of tags and branches we have in core,
so unfortunately we can't rely on it. I've also removed the thinkapp-based instructions about working with git,
since it's now fairly widespread knowledge, and better documented elsewhere.

Note that I've chosen to rename the "origin" remote to "upstream" in order to keep in line with
the contribution documentation on help.github.com (even if it's a bit more clumsy to explain upfront)
2016-11-15 17:36:43 +13:00
..
_images Swap out .Actions class for bootstrap .btn-toolbar (#5581) 2016-05-27 13:39:10 +12:00
00_Getting_Started Merge branch '3' 2016-09-14 11:49:07 +01:00
01_Tutorials Merge branch '3' 2016-07-20 21:44:47 +01:00
02_Developer_Guides Merge branch '3' 2016-11-10 01:09:35 +00:00
03_Upgrading Merge remote-tracking branch 'origin/3.1' into 3.2 2016-01-19 14:00:19 +13:00
04_Changelogs Added 4.0.0-alpha3 changelog 2016-11-03 15:27:10 +13:00
05_Contributing Use "composer update" in contrib docs 2016-11-15 17:36:43 +13:00
index.md DOCS 3.2 : fixing api: links now that api: tag parser working 2016-02-17 18:02:38 -07:00