![]() GitLab: self-managed runner for CI/CD jobs on GCP VM instances.GitLab: Continuous Deployment with Agent for Kubernetes and GitLab pipeline.GitLab: least privilege for Kube-API calls from GitLab Agent for Kubernetes.Bash: fixing SSH authentication error “bad ownership or modes for file/directory”.Vault: HashiCorp Vault deployed into Kubernetes cluster for secret management.Vault: Spring Boot web app using Spring Cloud Vault to fetch secrets.Bash: calculate sum from a list of numbers.Vault: NodeJS Express web app using node-vault to fetch secrets.Ansible: resolving error “Invalid callback for stdout specified: yaml”.Vault: JWT authentication mode with multiple roles to isolate secrets.Bash: schedule a command that will be run at reboot using cron.minikube: exposing a deployment using ingress with secure TLS.Vault: synchronizing secrets from Vault to Kubernetes using Vault Secrets Operator.Ubuntu: resolving systemd error, “Start request repeated too quickly”.Bash: indirect reference to evaluate a variable value.Git: cloning a git repository from one location to another.Git: Contributing to a git project using a pull request.Git: find branch name of newly applied tag.Git: BFG for removing secrets from entire git history.Git: Uploading an existing local project to GitHub from the console.Stackoverflow, is there way of introducing unrelated branch Github git, release notes for 2.23.0 where switch was introduced ![]() Stackoverflow, difference between git checkout and switch Stackoverflow,com, create empty branch on github Git merge my-fresh-branch -allow-unrelated-histories # this will fail! 'refusing to merge unrelated histories' If you want to merge this fresh branch into another, it will require the flag “allow-unrelated-histories”. Git push -u origin my-fresh-branch2 Merging this fresh branch into another branch Git commit -a -m "Initial commit on my-fresh-branch2" -allow-empty # checkout will not remove the files, so you must do this step manually If you are using a git client older than 2.23, use ‘git checkout’ like below. Git push -u origin my-fresh-branch Fresh branch using older ‘git checkout’ Git commit -a -m "initial commit of my-fresh-branch" -allow-empty # validate, no commit history on this branch Fresh branch using ‘git switch’ # create fresh branch The checkout command is still available, but it is no longer recommended to use it for switching branches.If you need to create a new git branch for your project, one that is completely fresh and with no previous history or commits, that can be done using the “orphan” flag of the switch command if you are using git 2.23+. The switch command is one of them-its sole purpose is to switch between branches. At some point, the Git team decided to split the command into several commands. It has tons of various options that let you run entirely different things: switch branches, reset code, etc. The checkout command has been a swiss army knife in the world of Git for a long time. We can use the switch command to switch between branches. To return to the latest version of our code, we need to switch to the default main branch. 02 Returning to the latest version in the main branch Note that the current content of the hello.html file is the content that we started with in the very beginning. Turn off this advice by setting config variable tachedHead to false If you want to create a new branch to retain commits you create, you mayĭo so (now or later) by using -c with the switch command. State without impacting any branches by switching back to a branch. You can look around, make experimentalĬhanges and commit them, and you can discard any commits you make in this
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |