On Wed, Nov 2, 2016 at 6:30 PM, awisnicki notifications@github.com wrote:
Great thank you. Does this mean that the way I tried to update them
yesterday on the site by using http://livingstonestage.lib.
umd.edu/admin/config/development/livingstone (which didn't work, ) will
now work?
OK, so two quick question as there are now six branchs to this repo. First, it looks like gh-pages are now in sync with dev/stage/prod. Is that correct? Second, henceforth we are only using dev/stage/prod, so I should ignore gh-pages. Is that correct?
Alter: https://github.com/livingstoneonline/LEAP-XSLT
To have three branches (dev,stage,prod) and add it's deployment to the deployment form in the admin section of the site.
Should be sorted now, branches added and deployment setup.
Great thank you. Does this mean that the way I tried to update them yesterday on the site by using http://livingstonestage.lib.umd.edu/admin/config/development/livingstone (which didn't work, ) will now work?
Yup
On Wed, Nov 2, 2016 at 6:30 PM, awisnicki notifications@github.com wrote:
##
Nigel Banks nigel.g.banks@gmail.com
OK, so two quick question as there are now six branchs to this repo. First, it looks like gh-pages are now in sync with dev/stage/prod. Is that correct? Second, henceforth we are only using dev/stage/prod, so I should ignore gh-pages. Is that correct?
We should always make
gh-pages
matchprod
, as the downloaded TEI documents themselves will point to thegh-pages
branch.gh-pages
is a special branch provided by github for hosting webpages.