Defect #11842
closed
Referencing issue in commit message not working.
0%
Description
I could swear this was working before, I can't precise when.
It doesn't seem to be working anymore.
Making references in the commits by using the specified keywords as defined in the Settings->Repositories for
- Referencing Keywords
- Fixing Keywords
doesn't seem to have any effect on the status of a given ticket.
Related issues
Updated by Paulo Castro over 12 years ago
SVN Version 10390
About your application's environment Ruby version 1.8.7 (x86_64-linux) RubyGems version 1.8.11 Rack version 1.4 Rails version 3.2.8 Active Record version 3.2.8 Action Pack version 3.2.8 Active Resource version 3.2.8 Action Mailer version 3.2.8 Active Support version 3.2.8 Middleware Rack::Cache, ActionDispatch::Static, Rack::Lock, #<ActiveSupport::Cache::Strategy::LocalCache::Middleware:0x7f9dda7aa588>, Rack::Runtime, Rack::MethodOverride, ActionDispatch::RequestId, Rails::Rack::Logger, ActionDispatch::ShowExceptions, ActionDispatch::DebugExceptions, ActionDispatch::RemoteIp, ActionDispatch::Callbacks, ActiveRecord::ConnectionAdapters::ConnectionManagement, ActiveRecord::QueryCache, ActionDispatch::Cookies, ActionDispatch::Session::CookieStore, ActionDispatch::Flash, ActionDispatch::ParamsParser, ActionDispatch::Head, Rack::ConditionalGet, Rack::ETag, ActionDispatch::BestStandardsSupport, OpenIdAuthentication Application root /srv/redmine/redmine Environment production Database adapter mysql Database schema version 20120731164049
Updated by Jean-Philippe Lang over 12 years ago
- Subject changed from Git referencing not working. to Referencing issue in commit message not working.
- Resolution set to Cant reproduce
- the exact commit message
- the exact values of your keywords in application settings
Updated by Paulo Castro over 12 years ago
Error log snippet.
Started GET "/projects/mycrazyproject/refatal: bad object f0b668c1a98b02b924728a7011feab8ce060fa3b
pository" for 192.168.13.3 at Sun Sep 16 23:43:57 +0100 2012
Processing by RepositoriesController#show as HTML
Parameters: {"id"=>"mycrazyproject"}
Current user: pecastro (id=3)
git log error: git exited with non-zero status: 128
Rendered repositories/_navigation.html.erb (27.1ms)
Rendered repositories/_breadcrumbs.html.erb (1.4ms)
Rendered repositories/_dir_list_content.html.erb (382.1ms)
Rendered repositories/_dir_list.html.erb (383.4ms)
Rendered repositories/show.html.erb within layouts/base (424.1ms)
Completed 200 OK in 2589ms (Views: 471.4ms | ActiveRecord: 31.2ms)
Referencing keywords: refs,references,IssueID
Fixing keywords: fixes,closes
Final stage of Plugin::STM done. closes #224
Have most,least and last return a hashref rather than a list. closes #160
return hashrefs of the elements keyed on their occurence index.. refs #208
Updated by Daniel Dehennin about 12 years ago
Hello,
We have the same issue, 16 of our projects have invalid git commitID in the redmine database, resulting in git log error: git exited with non-zero status: 128
For one project, we removed the git repository and add it again, redmine duplicates some issues notes and send duplicates email for automatic resolution of issues.
Is there a cleaner way to remove the faulty commitID from the database?
Regards.
Updated by Toshi MARUYAMA over 11 years ago
- Status changed from New to Closed
- Resolution changed from Cant reproduce to Invalid
Paulo Castro wrote:
Error log snippet.
git log error: git exited with non-zero status: 128
It is obviously git configuration problem.