19 Results
Pull requests do more than improve code quality. They expose how a team shares context, distributes ownership, and makes decisions. By looking at patterns in PR size, review participation, and response time, teams can better understand their dynamics and values in practice.
Reviewing pull requests doesn’t have to be time-consuming. Find out how using interactive rebasing to curate commits will keep your reviewer in the loop about your changes and reduce pull review process delays.
You may use Git to collaborate with your team, but are you using it to elevate your codebase’s history? Follow along to learn some advanced Git techniques like interactive rebasing.
Learn the pros and cons of using GitHub Wikis vs README files in your code, then walk through a GitHub Wiki tutorial.
Did you accidentally commit sensitive data? Learn how to scrub it from your Git repository and prevent committing sensitive data in the future.
How does your design system team notify subscribers that new features are being released, bugs are being fixed, or security holes are being patched? Patrick discusses versioning strategies and the advantages of automating that process.
Evaluating design system components with a scorecard can benefit subscribers by providing them with transparency and guidance for the developers creating those components.
Viewing Git as a SHA manager instead of as a source control file manager clears up a lot of confusion. Melissa shares some fundamental Git commands that help her manage SHAs in an enterprise-level project.
A great software build and deployment pipeline encourages collaboration and transparency. Here’s what we have found makes a successful pipeline.
Catherine takes an honest look at the the big three version control systems, comparing everything from usability and discoverability to third-party tool integration. Which service is right for your team?
