Is there any way that git-bug can show the github issue ID when it fetches the issues? I understand that supporting native commit tagging in git-bug itself is hard (issue #18) but it would be nice if we could get which ID github has assigned to the issue so that one can reference the issues in git commits and comments without having to open github.

Are you talking about showing the github ID when doing a git bug bridge pull or later when you display/edit an issue?

It would be most useful to show it when displaying or editing an issue. Because then, if I am working on a terminal only remote machine I could simply do a git bug show (or git bug termui) to see what issue # I need to reference in my commit to address an issue. So ideally it would be part of the issue metadata, like an "issue bridge ID" or something along those lines.

@Irubataru so you mean the issue Index and not the ID :) - I know nit picking

For github's purposes isn't it the same thing? I wasn't aware that github issues has an ID other than the issue index.

https://developer.github.com/v3/issues/#response it's called index number :)

EDIT: yes I'm missing the number too :sweat_smile:

I see. Anyway, I thought the idea could be generalised to other bridges as "how does the bridge reference this issue" is at could easily be a SHA etc with other bridges.

Each bridges, and the github one especially in this case store a bunch of metadata when importing an issue (see https://github.com/MichaelMure/git-bug/blob/master/bridge/github/import.go#L142-L143). So this could be exposed in the different UIs.

This bot triages untriaged issues and PRs according to the following rules:

• After 90 days of inactivity, the lifecycle/stale label is applied
• After 30 days of inactivity since lifecycle/stale was applied, the issue is closed

To remove the stale status, you can:

• Remove the lifecycle/stale label
• Comment on this issue

github-actions (github-actions) added label lifecycle/stale 1 year ago

This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:

• After 90 days of inactivity, lifecycle/stale is applied
• After 90 days of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

This bot will not automatically close stale issues.

To remove the stale status, you can:

• Remove the stale label from this issue
• Comment on this issue
• Close this issue
• Offer to help out with triaging

To avoid automatic lifecycle management of this issue, add lifecycle/frozen.

github-actions (github-actions) added label lifecycle/rotten 11 months ago

github-actions (github-actions) removed label lifecycle/stale 11 months ago

sudoforge removed label lifecycle/dormant 7 months ago

Hi, newbie here! I just learned about git-bug today and decided to try out the github bridge. It was easy to download the issues from my github repo. But indeed, I miss the github issue number. In fact, it is of crucial importance. With issues that have been open for more than a decade, the issue number has become part of the vocabulary when communicating with other developers. So, it is not just a number, it is more like a name. I don't want to start referring to issue #59 as f7ba3c or something...