# Export code using tags with subversion module **URL:** \ **Category:** Ansible Project\ **Created:** [May 2, 2014, 3:53pm UTC](https://forum.ansible.com/t/export-code-using-tags-with-subversion-module/15145 "2014-05-02T15:53:57Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Sam\_S](https://avatars.discourse-cdn.com/v4/letter/s/edb3f5/32.png) [@Sam\_S](https://forum.ansible.com/u/Sam_S)\ **Post date:** [May 2, 2014, 3:53pm UTC](https://forum.ansible.com/t/export-code-using-tags-with-subversion-module/15145/1 "2014-05-02T15:53:57Z")
So the doc shows the option to export code by passing a revision number. We deploy code by using the tags we create for deployments. Is it possible to use tags instead of “revisions,” or am I better off using the command line? ---
**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\ **Post date:** [May 2, 2014, 7:11pm UTC](https://forum.ansible.com/t/export-code-using-tags-with-subversion-module/15145/2 "2014-05-02T19:11:10Z")
svn doesn’t really have branches and tags, or it is more correct to say, they are an illusion and not really real. You would basically specify the tag to check out as the repo parameter. It’s beyond my place to say everyone can/should switch to git, but … if possible, and in a non-official capacity I highly recommend it – having real branches and smarter merging quickly makes up for the learning curve! ---
**Author:** ![Sam\_S](https://avatars.discourse-cdn.com/v4/letter/s/edb3f5/32.png) [@Sam\_S](https://forum.ansible.com/u/Sam_S)\ **Post date:** [May 5, 2014, 2:54pm UTC](https://forum.ansible.com/t/export-code-using-tags-with-subversion-module/15145/3 "2014-05-05T14:54:51Z")
I have a workaround and yes we’re eventually going to switch over to Git. We just need our devs to migragte their code to Github. 🙂