Project

General

Profile

Forums » Plugins »

Organizing a Git Repository for redmine plugin

Added by Travis Spangle about 9 years ago

I'm coming from an SVN background. My plugin is overwriting the Issues Show View. I would organize my repository so that Master would reflect Redmines Trunk. Then split out the different versions in branches. So redmine users 2.2-2.6 would have a branch. Then when the show.html.erb changes for 2.7 we would have a 2.7 branch.

Code changes are first committed to Master and are then merged into the branches. Is this the best way or does Git provide a more organized method?

My plugin is https://github.com/TravisSpangle/redmine_spent_time_in_issue_description


Replies (3)

RE: Organizing a Git Repository for redmine plugin - Added by Travis Spangle about 9 years ago

I've decided to implement a different mechanic. My views/issues/ directory has a show.html.erb for every revision I support: show.html.erb.11753, show.html.erb.12285, show.html.erb.13422, etc.

Then in my init.rb file I'll detect the current Redmine::VERSION.revision and cp the appropriate show.html.erb.revision as show.html.erb.

RE: Organizing a Git Repository for redmine plugin - Added by Travis Spangle about 9 years ago

I've created a patch requests for the needed hooks http://www.redmine.org/issues/19188. In the mean time I'll stick with the hack approach.

RE: Organizing a Git Repository for redmine plugin - Added by Travis Spangle over 8 years ago

How do I get my patch reviewed/accepted? It's been hanging in the breeze for 5 months now.

    (1-3/3)