Contributing to Rails? Start with the Gems You Already Use
summary
Shows actual pull request links and a QR code to slides and gives a concrete first step: pick gems already used, fix Ruby 3.4 warnings (frozen-string issues by using .dup, URI parser changes, bundled-gem warnings, hash inspect and error‑message diffs) and make CI green. Demonstrates GitHub Actions that enable -w and daily head/debug builds, runs released and development Rubies, tests with and without warnings, and explains when dev‑CI failures are acceptable and how to communicate and submit the first PR.
AI-written summary · about
chapters (8)
- 0:00Welcome
- 2:35Contributing to Rails difficulty
- 4:32Start with gems you use
- 7:26Ruby 3.4 fixes now
- 16:08Fixing CI for contributions
- 17:13CI types for gems
- 20:01Ruby CI setup
- 25:08Start contributing today
related talks
26mFrom 9-to-5 to Pull Requests: Sustainable Open Source Contribution
36mYour First Rails Pull Request
32mYour First Open-Source Contribution
35mYour First Open-Source Contribution
01h 22mBreaking Down the Barrier: Demystifying Contributing to Rails
29mTaking over Someone Else's Open-Source Projects
05mLightning Talk: gem-contribute Building what you cannot find
37mDon't touch that!
