Got a Pull Request for Diego? Learn the Why, What and How to Contribute to Diego
summary
Step-by-step workflow from opening a GitHub issue to a merged Diego pull request showing exact commands and checkpoints: clone CF release and Diego release, deploy a local BOSH Lite with vagrant, run unit suites, concourse jobs and acceptance cats tests, fork the submodule, write a failing test, implement the fix, squash and git rebase onto origin/master, force-push and update the PR. Covers common rejection causes (missing tests, conflicting roadmap work, untidy commits, failing CI) and automation like the CLA bot.
AI-written summary · about
chapters (8)
- 0:00Introduction to contributing
- 4:16Walkthrough of a contribution
- 8:06Setting up the development environment
- 15:12Forking and testing changes
- 18:07Reviewing and merging a PR
- 21:18Common reasons for PR rejection
- 23:25Getting started without a specific task
- 24:29Q&A on contributions
related talks
07mMy Path to Cloud Foundry Approver
32mContributing to Open Source: A Guide
43m'ProTalking' Your Way into Open Source
03mPull Requests Welcome! - How to Contribute to the Argo Community
18mHow to get your pull request merged
46mBuilding Developer Community One Pull Request at a Time
10mDemystifying Contributing to Open Source
32mYour First Open-Source Contribution