Feature #8624

revisions should always be automatically fetched

Added by Dave Abrahams over 11 years ago. Updated over 11 years ago.

Status:NewStart date:2011-06-16
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:SCM
Target version:-
Resolution:

Description

I consider it a usability bug that a project's changes/ and revisions/ URLs behave differently per #8610. People will notice the revisions/ URL in their browsers' address bars and assume—as I did—that it's a legitimate and reliable way to get to any revision in the repository. It should "just work."


Related issues

Related to Redmine - Defect #8610: Visiting revisions should try to update revisions before ... Closed 2011-06-15

History

#1 Updated by Dave Abrahams over 11 years ago

Oh, this is even worse than I thought it was. My original understanding, from what was said in #8610, was that if I was getting a 404 by going to https:// my-redmine-site /projects/xxx/repository/ revisions / some-SHA1 , that I could instead visit https:// my-redmine-site /projects/xxx/repository/ changes / some-SHA1 . But apparently I was wrong. I need to generate links into my repository browser from my automated test results page. Unless I can link to something that will cause changes to be fetched automatically, my users will get 404s and the system won't work for them. What should I do?

#2 Updated by Etienne Massip over 11 years ago

Set up some automatic fetch mechanism ?

Also available in: Atom PDF