Paul Wellner Bou paulwellnerbou

## delete_git_submodule.md

      
              1 file
            
          
              361 forks
            
          
              195 comments
            
          
              2382 stars
            
          
                myusuf3
                / delete_git_submodule.md
            
            
              Created
              November 3, 2014 17:36
            
              
                How effectively delete a git submodule.
              
          
    To remove a submodule you need to:

Delete the relevant section from the .gitmodules file.
Stage the .gitmodules changes git add .gitmodules
Delete the relevant section from .git/config.
Run git rm --cached path_to_submodule (no trailing slash).
Run rm -rf .git/modules/path_to_submodule (no trailing slash).
Commit git commit -m "Removed submodule "
Delete the now untracked submodule files rm -rf path_to_submodule


## pr.md

      
              1 file
            
          
              506 forks
            
          
              158 comments
            
          
              3659 stars
            
          
                piscisaureus
                / pr.md
            
            
              Created
              August 13, 2012 16:12
            
              
                Checkout github pull requests locally
              
          
    Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = git@github.com:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

  
## clean_code.md

      
              1 file
            
          
              1242 forks
            
          
              149 comments
            
          
              6151 stars
            
          
                wojteklu
                / clean_code.md
            
            
              Last active
              May 6, 2024 18:12
            
              
                Summary of 'Clean code' by Robert C. Martin
              
          
    Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules


Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

Design rules