Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

All development needs to happen in personal development branches.  You should be creating personal branches for your work.  Please review:

Github Fork-n-Beans Workflow

  • Once you are done, create a pull request in Github to merge into Dev.  
  • Ensure that you are keeping your personal branches up to date with the main dev branch so that your reviewer will only have to see your changes.
  • For each release, there must be a branch "release/x.y.z", all release branches must be merged back to "dev" branch.
  • Your PR will be the basis for kicking off a code review.  
  • In your PR, include the Jira ticket # in the comments.  
  • cc 'rchain-makers@pyrofex.net' 
  • Select a reviewer.
  • Wait for your reviewer's feedback.
  • Once approved, you will perform the merge to Dev.


In the event your PR wasn't created

It's likely that your change broke the build.  You can view the builds on Travis here:  https://travis-ci.org/rchain/rchain




  • No labels