New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
get code for custom linters working #6099
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @MichaelChirico and the rest of your teammates on Graphite |
0b1bd06
to
e9f3af2
Compare
Merge activity
|
@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. |
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. |
No description provided.