The information given on the git instrutions page for pushing a tag say:

git checkout 7.x-1.x
git tag 7.x-1.0
git push origin 7.x-1.0

However in the guide: Maintaining a project with Git ( the instructions are slightly different:

git checkout 7.x-2.x
git tag 7.x-2.0
git push origin tag 7.x-2.0

Note the inclusion of the 'tag' keyword in the second example.

I believe that the second version is the correct version? If so then the git instructions should be updated to this.


helmo’s picture

Both are technically correct. However the second is more specific, and slightly safer.

So +1 to change the instructions.

helmo’s picture

Assigned: Unassigned » eliza411

eliza411: What's your take on this?

eliza411’s picture

This is a newly introduced syntax. sdboyer and I would like to know when it was introduced in git before updating.

helmo’s picture

The documentation of this 'feature' in Documenation/git-push.txt was added in 2009 and is included in v1.6.1.3 by commit 803918462e58005d18c0ab63686dbd9e91330dfe.

When the actual feature was added will be somewhat harder to dig out.

eliza411’s picture

I think that's plenty :) I'll confirm with sdboyer, then make the update.

sdboyer’s picture

sure, that's plenty old enough. i'm fine with updating the docs to suit.

eliza411’s picture

Status: Active » Fixed

I've made this change. Sorry it took so long to get to and especially since the syntax turned out to be older than sdboyer originally thought :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

mayuri_02’s picture

Issue summary: View changes

HOw to convert Sanbox project to Full project once we pushed code using git.

opdavies’s picture

If you don't already have it, you will need to apply for permission to create full projects.