Re: Make gitlab automatically add MR ID to commit message(s)?

> The method I use is to go to > [https://gitlab.com/lilypond/lilypond/-/commits/master](https://gitlab.com/lilypond/lilypond/-/commits/master) > and search for the commit's title line using the search box in the > top right. For example, OK, thanks! Werner

Re: Make gitlab automatically add MR ID to commit message(s)?

Le dimanche 19 mars 2023 à 12:07 +, Werner LEMBERG a écrit : > ``` > > I think it would be beneficial if the original MR ID gets added to the > commit message(s).  Is this possible?  In many cases there is some > useful discussion that might help better understand code issue

Make gitlab automatically add MR ID to commit message(s)?

I think it would be beneficial if the original MR ID gets added to the commit message(s). Is this possible? In many cases there is some useful discussion that might help better understand code issues. Ideally, the 'merge request' button would do that. Werner

Re: [RFC] Commit message format

Jonas Hahnfeld via Discussions on LilyPond development writes: > For SHA1, I'd recommend using more than 6 chars to avoid collisions. > The Linux kernel encourages 12 characters [1], but I think we are good > with less. $ git log --oneline currently shows 10 chars for the > LilyPond repo, that sh

Re: [RFC] Commit message format

> upside: the number appears in git log —format=short > > > * The number is meaningless without the site that hosts the tracker > > exaggerated, but I see your point > > >Link to code review > >Link to issue > > > > By embedding the links, we

Re: [RFC] Commit message format

gt; Body > > Link to code review > Link to issue > > By embedding the links, we offer something clickable to whomever is > browsing the commit message. > > Somewhat relatedly, I would like to propose to use SHA1s + subject > lines to refer to previous changes, rathe

Re: [RFC] Commit message format

sts the tracker exaggerated, but I see your point >Link to code review >Link to issue > > By embedding the links, we offer something clickable to whomever is > browsing the commit message. -1, maybe. Will the commit messages be rewritten when we migrate to a different issue t

[RFC] Commit message format

Proposal === I would like to propose a different format, Subject Body Body Link to code review Link to issue By embedding the links, we offer something clickable to whomever is browsing the commit message. Somewhat relatedly, I would like to propose to use SHA1s + subject

Doc: CG: itemize section on commit message prefixes (issue 296810043 by paulwmor...@gmail.com)

Reviewers: , Message: Please review, thanks, -Paul Description: Doc: CG: itemize section on commit message prefixes Please review this at https://codereview.appspot.com/296810043/ Affected files (+20, -8 lines): M Documentation/contributor/source-code.itexi Index: Documentation

Re: Issue number in commit message (Fwd: [testlilyissues:issues] #4704 Improve beam count handling with subdivided beams)

Am 28.12.2015 um 16:33 schrieb David Kastrup: > Urs Liska writes: > >> Hi all, >> >> I've just pushed my patch for #4704, having reworked the branch to five >> discrete commits (removing detours but separating work on different >> files/tasks). >> >> However, I somehow managed to mix up the issu

Re: Issue number in commit message (Fwd: [testlilyissues:issues] #4704 Improve beam count handling with subdivided beams)

Urs Liska writes: > Hi all, > > I've just pushed my patch for #4704, having reworked the branch to five > discrete commits (removing detours but separating work on different > files/tasks). > > However, I somehow managed to mix up the issue number in several commit > messages, so only one commit

Issue number in commit message (Fwd: [testlilyissues:issues] #4704 Improve beam count handling with subdivided beams)

Hi all, I've just pushed my patch for #4704, having reworked the branch to five discrete commits (removing detours but separating work on different files/tasks). However, I somehow managed to mix up the issue number in several commit messages, so only one commit out of the list quoted below featu

Clarification for footnotes push commit message

Hey all, In the commit message about the footnote push, you'll see a line about TEST ONLY. What I mean here is that it is only 1/2 of the feature and thus should not yet be documented or considered complete (as discussed in previous emails). There is nothing test-ish about the implement

Re: commit message

Shure, no problem. I'll try to remember to document my commits better from now on. E On 30. jan. 2008, at 01:12, Han-Wen Nienhuys wrote: Hi Erlend, could you be a little more verbose in your messages? ** Fix issue 558 ** -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/

commit message

Hi Erlend, could you be a little more verbose in your messages? ** Fix issue 558 ** -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/list