<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/ruby-gems/chef.git/spec/data/git_bundles, branch https_shell</title>
<subtitle>github.com: opscode/chef.git
</subtitle>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/ruby-gems/chef.git/'/>
<entry>
<title>[CHEF-2420] Support annotated tags in the git provider</title>
<updated>2013-05-24T14:40:04+00:00</updated>
<author>
<name>Seth Falcon</name>
<email>seth@opscode.com</email>
</author>
<published>2013-01-30T06:03:49+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/ruby-gems/chef.git/commit/?id=8093045e9ce178bd82773ab3659787f48cfc0172'/>
<id>8093045e9ce178bd82773ab3659787f48cfc0172</id>
<content type='text'>
Annotated tags have their own SHA and also point to a SHA in the git
repo. Using git ls-remote $REPO $TAG* the tagged SHAs can be
identified by the '^{}' suffix appended to the corresponding tag name.

When resolving the remote reference, we now search for $TAG* and use
the SHA of the tagged commit (with ^{}) if it is there and otherwise
use the SHA with an exact match for $TAG (to avoid capturing anything
extra via the glob used to return refs).

If no revision is specified, we force 'HEAD' in the git ls-remote call
to constrain what can come back from the remote. Further, we protect
against a badly chosen annotated tag named 'HEAD'.

The functional test suite includes a git bundle of a small example
repo. We found that locally cloning this bundle provided the closest
simulation of `git ls-remote` behavior. YMMV depending on git version.

The test suite could be extended to improve overall coverage, but does
verify the desired behavior for annotated tags.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Annotated tags have their own SHA and also point to a SHA in the git
repo. Using git ls-remote $REPO $TAG* the tagged SHAs can be
identified by the '^{}' suffix appended to the corresponding tag name.

When resolving the remote reference, we now search for $TAG* and use
the SHA of the tagged commit (with ^{}) if it is there and otherwise
use the SHA with an exact match for $TAG (to avoid capturing anything
extra via the glob used to return refs).

If no revision is specified, we force 'HEAD' in the git ls-remote call
to constrain what can come back from the remote. Further, we protect
against a badly chosen annotated tag named 'HEAD'.

The functional test suite includes a git bundle of a small example
repo. We found that locally cloning this bundle provided the closest
simulation of `git ls-remote` behavior. YMMV depending on git version.

The test suite could be extended to improve overall coverage, but does
verify the desired behavior for annotated tags.
</pre>
</div>
</content>
</entry>
<entry>
<title>CHEF-3660: rename files that didn't play nice with git rebase</title>
<updated>2012-12-13T19:43:11+00:00</updated>
<author>
<name>sdelano</name>
<email>stephen@opscode.com</email>
</author>
<published>2012-12-13T19:43:11+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/ruby-gems/chef.git/commit/?id=b3a4d702ce636adfba5978fa5e3e8081328d7232'/>
<id>b3a4d702ce636adfba5978fa5e3e8081328d7232</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>[OC-4668] add functional tests for deploy_revision</title>
<updated>2012-11-05T22:34:06+00:00</updated>
<author>
<name>danielsdeleo</name>
<email>dan@opscode.com</email>
</author>
<published>2012-11-01T22:58:31+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/ruby-gems/chef.git/commit/?id=fa8cc55e5cec9791dade4333bc30a65d3ca4d6eb'/>
<id>fa8cc55e5cec9791dade4333bc30a65d3ca4d6eb</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
