Quantcast
Channel: A Frontend Engineer's Blog » quicktip
Viewing all articles
Browse latest Browse all 4

GIT Release Package Zip

0
0

On one of the projects I worked on previously I could develop a module independently. I had to develop independently for security reasons. This meant I had to use separate versioning for my code. I chose GIT. I prefer GIT to SVN for a few reasons.

This also meant that I had to hand over my module to the rest of the development team. The handover was a Zip-File containing my work. So how did I manage my handover packages?

Creating a Tag in GIT

When I was ready for the handover I made sure I was on the master branch and all the working features were merged with the master branch. The steps after that are described
below:

1. Created a tag with a comment

git tag -a Release-YYYYMMDD -m 'Customer preview release'

2. Push tag to the remote branch

git push --tags

Creating a Zip with GIT

1. Create zip-archive for the handover

git archive --format zip --output /PathTo/Release/Release-YYYYMMDD.zip master

Don’t forget the branch name master at the end.

2. Create a simple release documentation
To monitor the changes I also included a list of the files that had actually changed between two releases. There’s a nice handy git-command to do this.

Get all changes between two commits (use commit hashes):

git diff --name-only d20354c d6070d48

That’s it already!


Viewing all articles
Browse latest Browse all 4

Latest Images

Trending Articles





Latest Images