Modify ↓
Opened 13 years ago
Last modified 15 months ago
#10704 new enhancement
Plugin should ignore commits/revisions not in heads or tags
| Reported by: | Mitar | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-stable-1.6.x |
| Component: | plugin/git | Version: | 0.12.3 |
| Severity: | normal | Keywords: | refs branches tags |
| Cc: | mmitar@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
It seems plugin still (at least its 0.12 version) processes and adds to timeline all commits/revisions, even if they are not in heads or tags refs. From what I have read and by my experience this is wrong.
The difference is same as between:
git rev-list --all
and:
git rev-list --branches --tags
The point is that various git extensions are storing custom objects in other refs. For example, GitHub stores all pull requests (not even pulled in) in other refs. So if I have a mirrored GitHub repository and Trac access it I get all commits from all pending pull requests visible in timeline.
Attachments (0)
Change History (5)
comment:1 by , 12 years ago
| Keywords: | refs branches tags added |
|---|---|
| Milestone: | → next-stable-1.0.x |
comment:3 by , 8 years ago
| Milestone: | next-stable-1.0.x → next-stable-1.2.x |
|---|
Moved ticket assigned to next-stable-1.0.x since maintenance of 1.0.x is coming to a close. Please move the ticket back if it's critical to fix on 1.0.x.
comment:4 by , 5 years ago
| Milestone: | next-stable-1.2.x → next-stable-1.4.x |
|---|
Note:
See TracTickets
for help on using tickets.
We could make this configurable with a sane default.