"tox -e lint" is confusing if branch isn't up to date with trunk

[twisted-trac]

	@cjwatson reported
Trac ID	trac#9737
Type	enhancement
Created	2019-11-24 13:15:03Z

If trunk has commits that haven't been merged into the branch you're working on, then "tox -e lint" is confusing because it operates on the output of "git diff trunk", which diffs against the current trunk rather than against the common ancestor. Using "git diff $(git merge-base trunk HEAD)" instead would be 100% less confusing.

Searchable metadata

trac-id__9737 9737
type__enhancement enhancement
reporter__cjwatson cjwatson
priority__normal normal
milestone__None None
branch__ 
branch_author__ 
status__closed closed
resolution__fixed fixed
component__release_management release management
keywords__None None
time__1574601303270366 1574601303270366
changetime__1576475083875321 1576475083875321
version__None None
owner__Tom_Most__twm_____ Tom Most <twm@...>

[twisted-trac]

	@cjwatson commented

#1203

[twisted-trac]

	@twm set owner to @twm @twm set status to assigned

[twisted-trac]

	@twm removed owner @twm set status to new

Looks great, thank you! I love to see DX improvements like this.

#1203 (review)

[twisted-trac]

	@twm set owner to @twm @twm set status to closed

In changeset 0a0b59b

#!CommitTicketReference repository="" revision="0a0b59bf63473d521459025ba7ae060f98760000"
Merge pull request #1203 from cjwatson/9737-lint-dotdotdot

Author: cjwatson
Reviewer: twm
Fixes: ticket:9737

Run pycodestyle-twisted against merge-base with trunk