Explore >> Select a destination
|
You are here 
|
www.cyberdemon.org | ||
| | | | |
rgoswami.me
|
|
| | | | | A workflow for managing private submodules in a private repository without personal access tokens for Github actions Background Ever since Travis CI decided to drink corporate kool-aid, the search for a new CI has been brought to the fore again. Github Actions seem uniquely suited for private repositories, since most CIs bill for private repos. However, the basic authentication setup for the checkout action involves using one SSH key, effectively a personal access token, for both the main project and all submodules. | |
| | | | |
pbrisbin.com
|
|
| | | | | Git submodules are pretty great. They allow you to have nested git repositories so that modular parts of your app can exist as separate repos but be worked with as one file tree. Another benefit is that when submodules are pushed to github they appear simply as links to the repos they represent. If your not familiar, go ahead and google then come back - how submodules work overall is not the point of this post. | |
| | | | |
thork.net
|
|
| | | | | GM! Just a short note describing a recent new project of mine, git merkle (gm)! gm is a recursive tree of all the repos I've worked on since 2017 after a little spring cleaning; I removed about 40% of my pre-existing github repo history in the process of writing gm. | |
| | | | |
jaspervdj.be
|
|
| | | Hakyll - A Static Site Generator in Haskell. | ||
