Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow colon in closing issue from commit message #5699

Closed
2 of 7 tasks
znegva opened this issue Jan 11, 2019 · 2 comments
Closed
2 of 7 tasks

Allow colon in closing issue from commit message #5699

znegva opened this issue Jan 11, 2019 · 2 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality

Comments

@znegva
Copy link
Contributor

znegva commented Jan 11, 2019

  • Gitea version (or commit ref): 1.6.1
  • Git version: --
  • Operating system: --
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Gitea-Issues can be closed, reopened or referenced in commit messages.
The same keywords as in github are used, see here.
Githubs description of the feature is described here.

Inside github it is possible to use a colon between keyword and issue-number, eg

Fixed the critical bug
closes: #123

This is not possible with gitea, only keywords directly followed by the issue number are recognised:

Fixed the critical bug
closes #123

It would be great if an optional colon : could be supported.
If I read the source code correctly this should be feasible by slightly extending the regex used to detect the keywords.

Depending on your understanding, communication with the issue tracker is additional information that is not necessarily related to the actual commit.
Especially if you use the commit messages in addition in other ways (e.g. to create documentation or changelogs) issue-related stuff is often unimportant.
The ability to structure issue references more clearly makes it easier to ignore these references where they are not needed.

Additional Infos

@lunny lunny added the type/enhancement An improvement of existing functionality label Feb 7, 2019
@stale
Copy link

stale bot commented Apr 8, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Apr 8, 2019
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Apr 9, 2019
@stale stale bot removed the issue/stale label Apr 9, 2019
@guillep2k
Copy link
Member

Fixed by #7207?

@lunny lunny closed this as completed Sep 9, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality
Projects
None yet
Development

No branches or pull requests

3 participants