URLs similar to `https://develop.svn.wordpress.org/trunk@56994` have been used for a long time in auto-generated commit and merge messages (example).
I understand that URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org structure is used internally by SubversionSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. and perhaps some other tools; but the URLs don’t work in a browser or other httpHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. client:
% curl -I 'https://develop.svn.wordpress.org/trunk@56994' HTTP/2 404 server: nginx date: Mon, 20 Nov 2023 01:03:04 GMT content-type: text/html; charset=iso-8859-1 vary: Accept-Encoding
Is it possible for nginxNGINX NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. https://www.nginx.com/. to handle those URLs so they actually work, without interfering with Subversion or other tools?
One option might be to 302 redirect from
https://develop.svn.wordpress.org/trunk/?p=56994 (that second form appears to work as expected).
I suggested using a different format when generating commit messages, but this won’t deal with historical logs, emails, etc.
Detailed discussion here: https://wordpress.slack.com/archives/C02QB8GMM/p1698160954813579