This document discusses GitHub and open source software. It begins with an introduction to open source software, including its history and advantages. It then covers Git, including what it is, why it's used, and some basic commands. The document also discusses GitHub, including what it is, how it can be used for collaboration, and best practices. It emphasizes using commits and pull requests effectively, dealing with conflicts, using issues and labels properly, and choosing an appropriate license.

1. GITHUB AND
OPENSOURCE
By Kolawole Mangabo
INTRODUCTION TO GITHUB AND OPEN
SOURCE SOFTWARE

2. Agenda
● Birth and Rise of Open Source Software
● What is Git?
● Basics commands of Git
● GitHub
● Collaborations best practices with Git & GitHub

3. HI, I’M
KOLAWOLE,
Web Developer

4. BIRTH AND
RISE OF
OPEN
SOURCE
SOFTWARE

5. What is Open Source Software?
● Refer to a piece of Software both machine (object) and
human readable (source)
● Showed to the public on Internet and with few or no
restriction of reuse

6. Open Source History
● 1983: Launch of Project GNU by Richard Stallman
● Early 1990 : First Open Source Operating System
completely free (GNU/Linux)

7. Advantages of using OSS
● Access to code source
● Release cycles and bug fixes
● Security

8. What is Git?

9. What is Git?
● Most popular version control system
● Developed in 2005 by Linus Torvald and the Linux
community

10. Why use Git?
● Track the changes your make to files
● Revert to specific versions of your project
● Branching and Merge features
● Data Integrity

11. Basics Git
commands

12. Basics commands
● git init <name of the project>
● git clone <git:url>
● git add .
● git commit -am “message of commit”

13. Basics commands
● git push remote branch
● git pull remote branch
● git checkout branch | add -b to create a new branch
● git merge branch_to_merge

14. GitHub

15. GitHub
● Most used platform for OS projects
● More than 28M of users
● Good documentation
● Free with many features
● Integration options

16. GitHub
WALKTHROUGH

17. Collaborations
Best Practice
with Git-
GitHub

18. Commits
● Concise commit and clear messages
fixing issues fieldError because it affects the whole system
fixing issues fieldError
https://www.conventionalcommits.org/en/v1.0.0/

19. Push
● No push to master : NEVER
Neither no force push : rewrite history
Solution : git revert or git rm --cached

20. Pull
● pull rebase >>>>>> pull merge
Bad for the history : Messy graph
git pull --rebase=preserve

21. Conflicting Pull Request
● Grab the PR locally, merge and manually push
- git fetch origin refs/pull/23/head
- git checkout master
- git merge FETCH_HEAD
- Manually solve, add and commit
- git push origin branch

22. Issues
● Use predefined labels and alias code

23. Licenses
● No licenses is not “do what you want”
● Choose a license
● Read README.md and CONTRIBUTING.md
https://choosealicense.com/

24. GitHub Actions
● Make workflow automations easy
● Free plan
https://github.com/features/actions

25. @koladev32
@koladev
https://twitter.com/koladev32
https://medium.com/@koladev
onaelmangabo@gmail.com