PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

How Lyft Does Code Review

hackerone.com | blog | #code-review | #devops | #testing | #pull-request | #engineering-culture | #lyft
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

A look at Lyft's code review culture: strict ownership and review for tier zero services like ETA and mapping, mandated tests and Jira links, plus 'emoji-driven development' for pull requests.
Published
Collected

Related coverage

blog · hackerone.com
Reviewing One's Own Code
Before opening a pull request, developers should review their own code: shifting context, changing diff views, and pausing creates the cognitive distance to catch issues early.
blog · hackerone.com
Handling Code Reviews with Empathy
Explores handling code reviews with empathy, addressing how pull request conversations turn sour and how reviewers can give feedback that improves code without damaging working relationships.
blog · hackerone.com
Why Your Team Isn't Reviewing Pull Requests
PullRequest examines why teams leave pull requests unreviewed — usually avoidance, not invisibility — and offers actionable best practices for building a healthier peer code review culture.
blog · hackerone.com
5 Steps to Create an Effective Code Review Culture
Five steps to a healthier code review culture: keep pull requests small and well-described, tune the process for substantive feedback, and treat review as the team's most focused communication.
blog · borghq.io
How Automatic Retests Verify a Fix When Your PR Merges
How Borg's Odin verifies fixes when a linked pull request merges: it reviews the merged code change rather than the running app, deciding whether a finding is resolved, plus its limits.
blog · hacktron.ai
Introducing Hacktron Review
Hacktron Review is an AI security reviewer for pull requests that understands codebase context, reduces false positives, and catches exploitable vulnerabilities before they are merged.
Back