Explore >> Select a destination
|
You are here 
|
ljvmiranda921.github.io | ||
| | | | |
utf9k.net
|
|
| | | | | Why setting for one gitconfig when you could have two or more | |
| | | | |
embeddeduse.com
|
|
| | | | | We keep the source code of our applications and libraries in private repositories. Quite a few SoM and terminal makers do the same with their Yocto layers and their additional software. We typicall... | |
| | | | |
adventures.michaelfbryan.com
|
|
| | | | | When developing locally, you can add a private GitHub repository to your Rust crate as a git dependency and cargo should be able to retrieve it just fine. However, when you push your changes to GitHub and run CI, GitHub Actions can run into authentication issues when trying to build your crate. This is the error message I was fighting for a good part of today: $ cargo check --workspace --verbose --locked Updating git repository `https://github. | |
| | | | |
wittchen.io
|
|
| | | Short introduction Sometimes people need to specify multiple values for single .gitconfig file or they want to share just part of the configuration between two machines. There are different approaches for that. I can show you mine. Different configs for different Operating Systems On my private computer, I use Linux. I use Git for my private projects and I use my private e-mail address there. At the same time, I use Git at work on macOS with exactly the same Git configuration, but with a different e-mail... | ||
