-
Notifications
You must be signed in to change notification settings - Fork 166
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
doc: update ONBOARDING.md #1363
Conversation
Adds more concrete steps to the onboarding guide for the WG. This is updated with the information I used to onboard @mmarchini.
updated @Trott @mmarchini |
cc @LucaLanziani, anything else that should be added here that we went over? |
updated @LucaLanziani |
updated @mhdawson @joaocgreis, PTAL |
Since this has 6 approvals and has been open for about a week, will try and land this tomorrow assuming no other comments |
The section on pipelines is pretty important, there is definitely not consensus here that pipelines are a good idea as a "general trend". A couple of us have been highlighting how they can decrease usability for collaborators who just want to see test failure details. I'd rather than either not be included here or reworded to not make it sound like you should just assume pipelines are the way to go for everything. |
Updated to remove the pipeline/bash section from the guide |
ping @rvagg |
1 similar comment
ping @rvagg |
whoops! sorry @maclover7, +1 lgtm |
Landed in 4c5c10b -- thank you everybody for the review! |
Adds more concrete steps to the onboarding guide for the WG. This is
updated with the information I used to onboard @mmarchini.