From the course: GitHub Foundations Cert Prep by Microsoft Press

Unlock this course with a free trial

Join today to access over 25,500 courses taught by industry experts.

Explain the relationship of commits on a pull request

Explain the relationship of commits on a pull request - GitHub Tutorial

From the course: GitHub Foundations Cert Prep by Microsoft Press

Start my 1-month free trial Buy for my team

Explain the relationship of commits on a pull request

“

- [Tim] Here, I need you to understand, well, let me bring out my drawing tools to make it easier, that it's not always a one to one. What's that mean, Tim? In other words, you've got a feature branch where you've made your bug fix. One commit, PR done. I mean, yeah, that's the easiest, but it doesn't have to be that way, because the way it works in the real world, and I can attest this, I've lived this, is that you may have a PR that starts off in a draft state, you prepare it, maybe it has one or more than one commits. That's something else. We can absolutely stay on this branch and check it out, even after you publish your feature branch to GitHub, and you can add additional commits to it. Hopefully this will become clearer as we do demos and practice and keep recursing on this stuff.

Contents