Feature #4823
Don't evaluate commit-message "refs, closes, ..." when adding a repository
| Status: | New | Start date: | 2010-02-12 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | SCM | |||
| Target version: | - | |||
| Resolution: |
Description
The problem is like this:
- A project that uses redmine already is forked
- that project's repository contains commits with "refs #..." annotations
- when the repository-clone is added to another redmine (which already has issues), some issues will be closed / referenced mistakenly, as the issue IDs in the commit message is referencing an issue of a completely different redmine.
So it would be nice to have the option to skip that step when adding repositories.
Related issues
Associated revisions
Don't update issues nor log time when importing old changesets (#4823).
History
#1
Updated by Toshi MARUYAMA over 11 years ago
- Estimated time deleted (
0.50)
#2
Updated by Harry Garrood over 9 years ago
The fact that commit referencing keywords can be configured means that this can probably be closed.
#3
Updated by Toshi MARUYAMA almost 9 years ago
- Related to Defect #13762: SCM auto status change bypassses roles and permissions added