Opened 12 years ago
Closed 12 years ago
#10747 closed enhancement (wontfix)
Resolve ticket with git commit id
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | general | Version: | 1.0dev |
Severity: | normal | Keywords: | commit id git resolve |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Rather than have Trac look for the ticket number in the commit comments for automatic resolution, it would be preferable to be able to enter the commit id in the Trac ticket manually and then have it resolve automatically once the git commit is released.
This is preferable because it would
1) keep the commit comments in git clean 2) the commit comments may be lost in the merge process and not in the final release
Thanks
Attachments (0)
Change History (2)
follow-up: 2 comment:1 by , 12 years ago
comment:2 by , 12 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Replying to cboos:
Suggesting wontfix.
Same here. What's "releasing a git commit", anyway? Pushing it to a central location?
Interesting, but:
IRepositoryChangeListener
interface, much like the existing TicketCommit component doesWhile I see there can be setup where the two reservations above are not a problem, I don't think at this point this is common enough to be done in Trac core directly.
Suggesting wontfix.