Recommend full URI to issues instead of just the number

[underyx]

We always copy paste the entire URL to the issue in the last line instead of just #123.

1. This makes it easy to open the issue when you're browsing the repo somewhere other than your issue tracker — I could just cmd-click on Fixes https://github.com/slashsBin/styleguide-git-commit-message/issues/1 in the terminal while reading the git log.
2. It allows you to migrate to a new issue tracker (such as github to gitlab) without any confusion.

[underyx]

@slashsbin not interested in this change?

[slashsbin]

hi
I'm sorry for the delay, I was super busy with a new product launch.

Actually, I don't totally agree with you, although I agree that doing so will improve terminal log viewing.

Personally, for me, it's an overkill to paste the full URL because I need to copy/paste it from somewhere else beforehand.

Another thing is, doing so may break automatcally closing issues using keywords.

Maybe we should simplify browsing issues by other means like:

• PHPStorm: Issue Navigation
• iTerm2: Smart Selection & Triggers

What do you think?

[slashsbin]

It seems like GitLab is OK with automatic closing of issues by full URL.

[underyx]

GitHub is also okay with automatic closing by full URL. I also found that I almost never remember the issue number I'm working on so I need to copy-paste it anyway. Especially when working with three-four digit issue numbers.

…

On Wed, Aug 23, 2017, 9:14 AM Mohammad Shokri ***@***.***> wrote: It seems like GitLab is OK with automatic closing of issues by full URL <https://docs.gitlab.com/ee/user/project/issues/automatic_issue_closing.html> . — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#19 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABAuVAWvUrVnOHdCbADsJUqK-RGc99dqks5sa9FUgaJpZM4N-HE7> .

[slashsbin]

hi
please check rule#4.
any suggestions?

[underyx]

Perfect, we can consider this issue closed, thank you!