Integrator workflow

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages) The topic of this article may not meet Wikipedia's general notability guideline. Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted. Find sources: "Integrator workflow" – news · newspapers · books · scholar · JSTOR (August 2011) (Learn how and when to remove this message) This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Integrator workflow" – news · newspapers · books · scholar · JSTOR (September 2014) (Learn how and when to remove this message) (Learn how and when to remove this message)

Integrator workflow, also known as Integration Manager Workflow,^[1] is a method to handle source code contributions in work environments using distributed version control.

Frequently, in a distributed team, each developer has write access to their own public repository and they have read access to everyone else’s. There is also a dedicated repository, the blessed repository, which contains the "reference" version of the project source code. To contribute to this, developers create their own public clone of the project and push their changes to those. Then, they request one or more maintainers of the blessed repository to pull in their changes.

• GitHub
• Bitbucket
• CodePlex

This computer-engineering-related article is a stub. You can help Wikipedia by expanding it.

• v
• t
• e