[wp-meta] [Making WordPress.org] #1502: Add redirects for URLs referenced in git-svn-id

[Making WordPress.org]

#1502: Add redirects for URLs referenced in git-svn-id
-------------------------+---------------------
 Reporter:  morganestes  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  lowest       |   Milestone:
Component:  Trac         |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by morganestes):

 Replying to [comment:2 obenland]:
 > Where are these links shown and what exactly needs changing?

 When I first saw them, they were exposed in my IDE as part of the Annotate
 feature (in PhpStorm). They come from the commit log, so inside the
 develop repo, running `git log src/index.php` returns `git-svn-id` as part
 of each commit:


 {{{
 $ git log src/index.php
 commit 8f95800d52c1736d651ae6e259f90ad4a0db2c3f
 Author: Gary Pendergast <pento at git.wordpress.org>
 Date:   Thu Nov 30 23:09:33 2017 +0000

     Code is Poetry.
     WordPress' code just... wasn't.
     This is now dealt with.

     Props jrf, pento, netweb, GaryJ, jdgrimes, westonruter, Greg Sherwood
 from PHPCS, and everyone who's ever contributed to WPCS and PHPCS.
     Fixes #41057.



     git-svn-id: https://develop.svn.wordpress.org/trunk@42343
 602fd350-edb4-49c9-b593-d223f7449a82

 commit 8d72ad52ff6a37f235ac585abef1131183d0e548
 Author: Andrew Nacin <nacin at git.wordpress.org>
 Date:   Wed Sep 25 00:17:40 2013 +0000

     Don't rely on include_path to include files.

     Always use dirname() or, once available, ABSPATH.

     props ketwaroo, hakre.
     fixes #17092.


     git-svn-id: https://develop.svn.wordpress.org/trunk@25616
 602fd350-edb4-49c9-b593-d223f7449a82

 commit b43712e0f79a9f5bea52217e06155e2f471c490c
 Author: Andrew Nacin <nacin at git.wordpress.org>
 Date:   Wed Aug 7 05:25:25 2013 +0000

     New develop.svn.wordpress.org repository based on the old core.svn
 repository.

      * All WordPress files move to a src/ directory.
      * New task runner (Grunt), configured to copy a built WordPress to
 build/.
      * svn:ignore and .gitignore for Gruntfile.js, wp-config.php, and
 node.js.
      * Remove Akismet external from develop.svn. Still exists in core.svn.
      * Drop minified files from src/. The build process will now generate
 these.

     props koop.
     see #24976.

     and see http://wp.me/p2AvED-1AI.



     git-svn-id: https://develop.svn.wordpress.org/trunk@25001
 602fd350-edb4-49c9-b593-d223f7449a82
 }}}

 Since they represent links to actual changesets, I'd like to see them
 redirected instead of just die on the vine. My guess is an .htaccess
 rewrite rule on the Subversion server could do the trick, but should it go
 to the SVN revision or the Git one?

 If you want to redirect to the SVN revision viewer, then this could work:

 {{{
 RewriteRule ^trunk@([0-9]{1,6})$ /!svn/bc/$1/
 }}}

 Rewriting to Git/Trac would be:

 {{{
 RewriteRule ^trunk@([0-9]{1,6})$
 https://core.trac.wordpress.org/changeset/$1
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/1502#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org