Ikuru K made their first pull request to contribute a patch allowing software rendering of an OpenGL demo program on machines with Mesa 10.3.2. They cloned the repo, found it did not run, raised an issue on GitHub, got a reply, tested a suggested fix, then submitted a pull request with two commits - one to set an environment variable and another to update the README. The maintainer asked them to squash the commits together which they did by merging and pushing to their branch, and their contribution was merged.

1. My First Real Pull Request
Ikuru K

2. What was it that I did?
● Christopher Wellons' (@skeeto) opengl demo
did not run on my old machine.
● I created a patch that allows software rendering
of the program for machines that have mesa
10.3.2

3. Flow of the story
● Read the interesting blog post
<http://nullprogram.com/blog/2015/06/06/> and
decided to try it on my machine.
● Git-clone'd the repo, ran the code and got
initialization failed message.

4. Raised an Issue on Github

5. Got an immediate reply

6. Did as he suggested, and it worked!

7. Made a pull request so that
environment var is set by make it
self
● https://github.com/skeeto/opengl-demo/pull/4

8. Got a suggestion that I should also
mention as such in README, so
made another commit

9. @skeeto said he will merge my
contribution if I squash the two
commits together!

10. How I squashed commits
● Checked out head of @skeeto's master
● Did: merge –squash <mybranch>
● And pushed to the branch that I have requested
the pull

11. Merged! But...?

12. Resulting Commit After @skeeto
adjustment
● https://github.com/skeeto/opengl-
demo/commit/c2373b8d941c18bd3b4deaf438f4c60ff0df8e98

13. Lessons Learned
● Casually raising issues on Github is a nice thing
that I do not need to be shy about.
● Proper commit messages are important, also
for commits being squashed.

14. ● Thanks, especially to @skeeto for the valuable
lesson!