Hi Sam!Thanks for your email - I think it wouldn't be too hard to have a pass on the commit message and transform all Rust-GCC/gccrs#ISSUE_NUMBER instances into https://github.com/rust-gcc/gccrs/issue/ISSUE_NUMBER just for the email. I'll have a look if Marc doesn't beat me to the punch :)
And thank you for your comment regarding adding more context to commit messages - I'll keep an eye out when reviewing PRs moving forward.
Kindly, Arthur On 4/18/26 5:43 PM, Sam James wrote:
[email protected] writes:From: fisnikhasani <[email protected]> Fixes: Rust-GCC/gccrs#4503I have two suggestions for these to help make them more useful from the mailing list side: 1) Could you please consider requiring full links for issues or pull request references in URLs? It means they're clickable outside of GitHub (including in a mirror), and also means references will work if gccrs ever moves elsewhere. 2) The rustc folks tend to not write very much in commit messages, in part because of their GitHub-centric workflow. It'd be appreciated if commit messages could contain some of the what and why. (The main team usually have these just fine, just contributors don't tend to realise the need for it.) Thank you!
OpenPGP_0x1B3465B044AD9C65.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
