Channels ▼
RSS

Tools

Sharpened Forking Inside Git


Atlassian has announced Stash 2.4 as an update to its on-premise Git repository management system for enterprise developer teams.

More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

This release adds support for forking distributed development workflow practices popularized in open source development, along with per-repository permissions.

Stash 2.4 helps development teams set up distributed code collaboration workflows that offer open source-style development flexibility with the security permission control.

Atlassian's Giancarlo Lionetti says that development teams can now replicate the benefits of an open source model with the security they need to maintain control and accountability. "The new features in Stash 2.4 include fork support so that any user can fork a project through Stash, insulating code from the original author to unwanted changes or errors. The original author can receive feedback or improvements in the form of pull requests."

Personal repositories also feature here so that developers now have the freedom to innovate and store their private snippets of work, kick-start their own project, contribute a bug fix for a project they are not a member of, or add a feature to a common component maintained by a small group in an organization.

Stash accommodates any Git development workflow an enterprise development team may choose. Enterprise teams building software can now set up controls or permissions at the project, repository, or branch level, increasing both development and administrative flexibility.

For example, with repository permissions, administrators can restrict access to specific repositories for new developers or contractors, permitting them only to view a repository or fork the code (make a copy on the server-side) to work on it separately without risk to the master repository. Through a pull request, these restricted developers then ask for permission to contribute. Stash enables developers to "innovate and create code" within the requirements established by the team lead or repository manager.


Related Reading






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video