= Information for Trac Hack Developers = == Subversion == The TracHacks Subversion repository is at http://trac-hacks.org/svn. Each hack has its own top-level path, with sub-directories underneath each directory for each [wiki:release] the hack is available for. eg. http://trac-hacks.org/svn/addcommentmacro/0.9 [[BR]] http://trac-hacks.org/svn/addcommentmacro/0.8 When a NewHack is registered, the developer is given write access to the entire path underneath their hack, so these are just default directory layouts. TracHacks has the [http://projects.edgewall.com/trac/file/tags/trac-0.8.4/contrib/trac-post-commit-hook trac-post-commit-hook] installed, so you can use the handy ''closes #x'', etc. when committing changes to the repository. == Issues == If you have any issues with TracHacks, check the [report:9?COMPONENT=TracHacks existing tickets], then [http://trac-hacks.org/newticket?component=TracHacks&owner=athomas create a ticket]. If all else fails, contact [wiki:athomas me]. == Meta-tags == TracHacks uses a couple of [wiki:metatag metatags] when creating new hacks; [wiki:release release] and [wiki:type type]. If a tag page (eg. [wiki:macro macro]) is itself tagged with one of the meta-tags, it will be included as an option in NewHack. '''''Please don't abuse this.''''' Additionally, any tag whose tag page is itself tagged with [wiki:metatag metatag] will be excluded from the NewHack list of additional tags. That's quite a confusing sentence, so just take a look at [wiki:type type] for an example. == Newbie Corner == * Setup your development environment * Check out [wiki:Tutorials] created by our contributors * Hack away!