Skip to content
This repository was archived by the owner on Feb 2, 2022. It is now read-only.

Repository structure

Jump to bottom
Meitar M edited this page May 7, 2016 · 2 revisions

Wiki ▸ Documentation ▸ Developer Documentation ▸ Repository structure

Our project repository maintains a structure that mimics git-flow. We encourage individual contributors to use the fork-and-pull workflow (aka "forking workflow") when working on patches or to suggest pull requests.

  • The master branch should always contain code that is "production-ready" (or as close to that as is reasonable before an official stable release is announced).
  • The develop branch contains the latest integrated code.

Every push or pull request to these branches is automatically built and tested by Travis-CI against the (PHPUnit) unit tests defined in the repository's tests/ directory.

Questions? Double-check the Frequently Asked Questions. Otherwise, if you want help from other users, try the Buoy Support Forum. To contact the developers, open a new issue.

Home

About Buoy

Documentation

For community members

For website admins

For project contributors

Meta

Clone this wiki locally