Re: Automatic URLs in forgejo? (was Re: Sourceware forge experiment)

"Richard Earnshaw (lists)" <[email protected]>
Newsgroups gmane.comp.lib.glibc.alpha,gmane.comp.gnu.binutils,gmane.comp.gcc.devel,gmane.comp.gdb.devel,gmane.comp.lib.newlib
Message-ID <[email protected]>
On 24/10/2024 16:29, David Malcolm wrote:
> On Mon, 2024-10-21 at 03:22 +0200, Mark Wielaard wrote:
>> As an experiment Sourceware is now running an forgejo v9 instance at
>> https://forge.sourceware.org
>>
>> Everybody with an @sourceware.org, @cygwin.com or @gcc.gnu.org
>> address
>> can register an account (please use the same user name as your
>> account
>> name).
>>
>> The setup has disabled most "extras" (no badges, stars, issues,
>> wikis,
>> packages, timetracking, milestones, etc.). And users can only fork
>> existing repos (it has mirrors of various sourceware projects). Some
>> things haven't been setup yet (external trackers/bugzilla, incoming
>> email, ci, etc.)
>>
>> The full setup can be found in this git repository:
>> https://sourceware.org/cgit/forge/
>>
>> For now it is only open for existing maintainers/developers for
>> experimentating with a pull-request model. We can add others as long
>> as they understand this is an experiment and does not mean projects
>> are accepting patches through it. Contributions should still be sent
>> through the mailinglists.
>>
>> There is also a new mailinglist for discussion about the setup and
>> the
>> best way to create a pull-request workflow. Please subscribe if you
>> create an account and mention which project/organization you would
>> like do some experiments for. We can then add you to that
>> organization.
>>
>> https://sourceware.org/mailman/listinfo/forge
> 
> Thanks for setting this up.
> 
> How easy would it be to set up automatic URL generation in the web UI
> from regexes on the text of commit subjects/message? 
> 
> GCC has its own short notation for referring to commits, see e.g. 
> 
> https://forge.sourceware.org/gcc/gcc-mirror/commit/83abdb041426b7490e93c3f77be93148bcd94de3
> where I wrote:
> "I believe this hasn't been necessary since r15-1413-gd3878c85f331c7."
> It would be nice if the "r15-1413-gd3878c85f331c7" were to get auto-
> urlified in the web UI to
> https://forge.sourceware.org/gcc/gcc-mirror/commit/d3878c85f331c7
> 
> Similarly, in GCC we use the notation PRnnnnnn or PR component/nnnnnn
> to refer to "problem reports" in bugzilla.  Looking at e.g.
> https://forge.sourceware.org/gcc/gcc-mirror/commit/65c5bbe1c92f9c08e99d3a37c136f2ef9804a37f
> it would be nice if the "PR114423" in the subject line and the 
> "PR preprocessor/114423" in the ChangeLog fragments in the commit log
> got auto-urlified in the web UI to:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114423
> 

See the wiki page I added today for setting up bugzilla (gcc.gnu.org/wiki/ForgeExperiment).  It only works for the <component>/<id> style due to limitations in the way forgejo uses the regex groups.


> Other projects sharing the forgejo instance have other notations,
> policies, and bug tracker instances, of course.
> 
> FWIW I seem to recall seeing something like this working in the
> instance that was recently demoed at Cauldron.
> 
> Hope this is constructive; thanks again
> Dave
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.