|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #80684 Make bug "Closes" action more strict for bugtrack
Submitted: 2021-01-28 19:12 UTC Modified: 2021-01-28 22:33 UTC
Avg. Score:1.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:0 (0.0%)
Same OS:0 (0.0%)
From: Assigned:
Status: Open Package: *General Issues
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2021-01-28 19:12 UTC]
A commit message with "Closes php/doc-pt_br#3" correctly closes the respective issue on GitHub doc mirror, but also try to close a bug. See transcript bellow:


Commit:    dd831989aec8cc8f6ed5682f2f7f02e62b909352
Parents:   6be11c70ce382a1edb06c2084072c6857df04797
Branches:  master


Update translation

Closes php/doc-pt_br#3


Expected result:
No mention of "Bugs:" or ""

Actual result:
Trying to re-closes a ancient


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2021-01-28 22:33 UTC]
I agree that the hash sign followed by a number anywhere in the
commit message should generally not close a bug ticket, but at
least in this case you could have just used

    Closes GH-3.

There is no need to mention the repo, or write a hash sign. :)
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Tue Feb 27 23:01:27 2024 UTC