ReinsBrain / adventuretoursgroup

0 stars 0 forks source link

Make webstaging for every pull request #77

Closed oreyes1991 closed 4 years ago

jegj commented 4 years ago

@oreyes1991 @samo1811 will be helpful some documentation about the ticket and what do you need :smile: .... do you need a staging version of the website based on the staging branch ??? please confirm... because each pull request create a site on AWS S3 like this( check slack channel - tepago_pro-ci)

(staging) -> pull request # 22 http://tepagopro-22.s3-website-us-west-1.amazonaws.com/tepago.html (prod) -> develop will change to master in the future https://rebelstackio.github.io/tepagopro/

NOTE You shoul add the tepago.html at the end on the staging web sites. You Should check you build process and fix the naming for the files

oreyes1991 commented 4 years ago

@jegj yes sorry, as @ReinsBrain told us we need a staging for pull requests, Production branch is master, but all pull request are made to develop branch those are the ones that nee to be reviewed by @cmexcel or @Lcup837 .

By now is fully static page see #75

jegj commented 4 years ago

@oreyes1991 @samo1811 That behavior is already done and fixed yesterday based on ticket https://github.com/rebelstackio/tepagopro/issues/23. To activate the deploy again for that pull request, please rebase the target branch with the lastest version of develop and push it with -f:

git rebase develop
git push origin <target_branch> -f

Tha should be enought to deploy a new site with the content on your staging site

Closing this issue. Please re-open it if that doesn't work

jegj commented 4 years ago

Sorry i was confused ... thought the ticket is related with the tepagopro repo that already have the pullrequest system. Going to add it to this repor

jegj commented 4 years ago

Closed by #82