Opened 10 years ago
Last modified 7 years ago
#1861 new enhancement
github hook should optionally ignore distinct=false
Reported by: | dustin | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 0.9.+ |
Version: | 0.8.3p1 | Keywords: | git |
Cc: |
Description
See https://github.com/blog/807-new-and-improved-service-hook-payloads
non-distinct commits are likely to have already been built, and thus not need to be built again.
Also, we should ignore branch deletions.
Change History (3)
comment:1 Changed 10 years ago by tom.prince
comment:2 Changed 10 years ago by dustin
- Milestone changed from 0.8.4 to 0.8.5
comment:3 Changed 7 years ago by dustin
- Milestone changed from 0.8.+ to 0.9.+
Ticket retargeted after milestone closed
Note: See
TracTickets for help on using
tickets.
I agree that this should be exposed. I am not entirely sure how though, since multiple repositories may use the same hook, but want different settings.