OPEN SOURCE CONTRIBUTION

Original post link:
https://linkedin.com/feed/update/...

Start your open source journey.

To Push your personal project to GITHUB.
1. git init
2. git remote add origin [link]
3. git add .
4. git commit -m "commit message"
5. git push origin master

To contribute to someone else project use the following steps:
1. Fork the repo.
2. Clone the project in your local directory using git clone [link]
3. After clone, create a new branch. git branch [branch name]
4. Checkout to new branch created using: git checkout [new branch name]
5. Make changes in Project then 'git add' and 'commit'
6. Push back the changes using git push origin [newbranch name]
7. Open Github web view and click the pull request button and you are done.

Follow Up Post: https://lnkd.in/fEMbTPC

GitHub Link of GIT-CHEATSHEET: https://lnkd.in/fhy4hmu

HD VIDEO: https://lnkd.in/fmq8GTd

Remember this : https://devrant.com/rants/1547095/... ?

FINALLY some updates.

Just to say they deleted the branch I was trying to merge on during the month, so I need to redo the pull request and rebase.

(ﾉ｀□´)ﾉ⌒┻━┻

When I do SSH to a remote server, how can I show git branch name?
When I SSH it shows me this:
admin@123.456.789.555:/home/some_folder$

Can I configure it to show something like oh-my-zsh that shows me the current Git branch I am pointed to?

This is my local iTerm zsh default theme:
some_folder git:(feature/some_branch_name)

To branch or not to branch? (in developing software multiple features, releases...) (git)

I've been searching a lot of posts and info on the internet ( http://bit.ly/2kBLcar http://bit.ly/197szRP ). In summary, some people say it is better to branch and others the opposite. What do you think?

My conclusion was: let's branch but let's merge periodically to minimize merge conflicts.