Github does not provide such functionality. Github repositories are either public or private, both not both. However, if the part you want to share is small enough (let’ say 4-5 files) you can create a public gist. Unfortunately, there is no way to update the gist automatically.
To get a git history without any pull request merge commits I can use the merge button (Pull request page) and perform a rebase and merge:
This answer was mostly derived from Git Pathspecs and How to Use Them. I haven’t copied everything over, so look into the link to dig deeper The pathspec is the mechanism that git uses for limiting the scope of a git command to a subset of the repository. If you have used much git, you … Read more
You won’t lose commits by closing the terminal. ctrl+c will exit the prompt > What happened was you opened up a string with the odd number of ‘ characters. Bash expects more input for your string, and allows you to enter it after the > prompt. Try typing ‘ and hit return, you will get … Read more
git push assumes that you already have a remote repository defined for that branch. In this case, the default remote origin is used. git push origin master indicates that you are pushing to a specific remote, in this case, origin. This would only matter if you created multiple remote repositories in your code base. If … Read more
Git branches do not have “heads” in the Mercurial sense. There is only one thing called HEAD, and it’s effectively a symlink to the commit you currently have checked out. In the case of hosted repositories like GitHub, there is no commit checked out—there’s just the repository history itself. (Called a “bare” repo.) The reason … Read more