• Run linters on test scripts #6121
• New linter for test(symbol) #6120
• customize lengths_linter for data.table usage #6100
• get code for custom linters working #6099 👈
• Use R 3.2.0 features #5838
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MichaelChirico and the rest of your teammates on Graphite

Merge activity

• May 4, 12:06 PM EDT: @MichaelChirico started a stack merge that includes this pull request via Graphite.
• May 4, 12:09 PM EDT: Graphite rebased this pull request as part of a merge.
• May 4, 12:10 PM EDT: @MichaelChirico merged this pull request with Graphite.

@jangorecki FYI. My first time merging a stack all-at-once, we see here that under-the-hood, Graphite is just force-pushing after merging an "up-stack" PR, likely as a way to bulldoze through conflicts after rebase.

Thanks for info. I am not really convinced about using graphite. It creates higher barrier for entry for new contributors. I would definitely go for it when there is team of full time developers, but in situation where we want to attract new volunteer contributors it can be less beneficial.

It creates higher barrier for entry for new contributors.

I definitely agree with that. currently I'm only using it for ½ or fewer of PRs, wherever a chain feels appropriate. the rest remain in pure git+GitHub. new contributors don't have to know about graphite.