https://gitlab.synchro.net/main/sbbs/-/issues/1#note_990

Ok, clearly we can't use the number sign in commit messages... this is pretty silly.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/issues/1#note_991

hmm interesting, at work we use number signs all the time in commits. that is how we link them to jira ticketing system

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/issues/1#note_992

We can use them, but the associated commits are being added as notes/comments on this closed issue. Presumably, because it's issue number 1. Specifying a number after a number sign in a commit message will do something different and expected.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

update https://gitlab.synchro.net/main/sbbs/-/issues/1

<DigitalMan> term Node 1 <Digital Man> !JavaScript s:\sbbs\exec\fseditor.js line 330: TypeError: line[l + 1] is undefined

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/issues/1#note_994

I turned notifications for this issue off and locked it. Hopefully that helps.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

On 11/28/2020 4:17 PM, Deuce wrote:

https://gitlab.synchro.net/main/sbbs/-/issues/1#note_990

Ok, clearly we can't use the number sign in commit messages... this is pretty silly.

Using # at the beginning is treated as a comment, this is useful as merge/rebase/ammend will show a commented out list of files effected, etc.

If you use # in a string...

ex: Fixes for #122

Gitlab will associate the commit with issue/bug #122

--
Michael J. Ryan
tracker1 +o Roughneck BBS
---
­ Synchronet ­ Roughneck BBS - roughneckbbs.com