Ticket/Issue ID #148

New Issue

GiteaMirror · 2026-02-17T11:49:42-06:00

GiteaMirror commented

2026-02-17 11:49:42 -06:00

Originally created by @jamesgeddes on GitHub (May 15, 2022).

Where should the issue ID go? Is there a convention for what the tag should be?

Would this be satisfactory?

fix: title

body

issue: {id}

Originally created by @jamesgeddes on GitHub (May 15, 2022). Where should the issue ID go? Is there a convention for what the tag should be? Would this be satisfactory? ``` fix: title body issue: {id} ```

GiteaMirror closed this issue

2026-02-17 11:49:43 -06:00

GiteaMirror commented

2026-02-17 11:49:44 -06:00

@damianopetrungaro commented on GitHub (May 15, 2022):

Hey @jamesgeddes there is an example on the website you could use as a reference:

fix: prevent racing of requests

Introduce a request id and a reference to latest request. Dismiss
incoming responses other than from latest request.

Remove timeouts which were used to mitigate the racing issue but are
obsolete now.

Reviewed-by: Z
Refs: #123

you could add Issue: id as a footer element :)

@damianopetrungaro commented on GitHub (May 15, 2022): Hey @jamesgeddes there is an example on the website you could use as a reference: ``` fix: prevent racing of requests Introduce a request id and a reference to latest request. Dismiss incoming responses other than from latest request. Remove timeouts which were used to mitigate the racing issue but are obsolete now. Reviewed-by: Z Refs: #123 ``` you could add `Issue: id` as a footer element :)

GiteaMirror commented

2026-02-17 11:49:44 -06:00

@jamesgeddes commented on GitHub (May 15, 2022):

Thanks @damianopetrungaro - I had seen that but it seemed like Refs is for git IDs, so I was just wondering if it would be permissible to make up a tag. We will do as you have suggested! Thanks!

@jamesgeddes commented on GitHub (May 15, 2022): Thanks @damianopetrungaro - I had seen that but it seemed like `Refs` is for git IDs, so I was just wondering if it would be permissible to make up a tag. We will do as you have suggested! Thanks!

GiteaMirror referenced this issue

2026-02-17 11:58:47 -06:00

[PR #148] [MERGED] build: Update deps #317

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#148