Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings
campgurus edited this pageAug 11, 2015 ·6 revisions

We are currently using thefeature branch workflow for individual branches to merge into master when done.

We're currently ironing out challenges with our multiple stage heroku environment, and we're looking at both the workflow described inGit Flow considered harmful and theGithub Workflow documents.

We currently:

  1. Work on feature branches until they are satisfactory per rspec and local browser testing

  2. Push individual branches out toTravis to test

  3. Merge back into master when finished and tested successfully

  4. Test & Confirm onTravis

  5. Deploy to Staging (since it's heroku, wegit push but do notgit push -f

  6. Do acceptance testing on Staging

  7. Tag Release

  8. Deploy to Production (@trystant manages merges to the master branch and production deploys)

More info on these steps is forthcoming

Clone this wiki locally

[8]ページ先頭

©2009-2025 Movatter.jp