Eyar Zilberman

Running schema validation tests is important, and the sooner the better. If all machines (local developers environment, CI, etc.) have access to your Kubernetes cluster, run `kubectl --dry-run` in server mode on every code change. If this isn’t possible, and you want to perform schema validation tests offline, use kubeconform together with a policy enforcement tool to have optimal validation coverage.

In this article we share 5 examples of Kubernetes misconfiguration mistakes. They were all fairly simple as far as mistakes go but did impact production.

One of the best ways to tame the complexity around your Kubernetes clusters is by correctly leveraging labels on all your resources. There are lots of benefits to using labels and we’ll try to touch on most of the big ones in this article.

You can now use GitHub Actions to make CI/ CD pipelines. Read 7 GitHub Actions best practices you should adopt, including on dependencies, secrets, and more.

So you wish to do "git create branch branch-name"? This tutorial will show you the right git commands for creating branches, naming and renaming git branches.

So you wish to "git unstage" files in git? This tutorial will show you the right git commands to remove all or specific staged files from index.

So you wish to "git undo merge" in git? This tutorial will show you the right git commands to cancel a merge to master, even after it’s been committed.

So you wish to "git remove untracked files"? This tutorial will show you the right git commands to remove unused files in your working directory.

So you wish to do a "git force pull"? This tutorial will show you the right git commands to discard your local changes and replace them with your latest commit.

If you’re using AWS Lambda functions, there’s a chance that you recently got an email about Node 8.10 reaching the end of its life. Learn what it means and what you should do next to be prepared to migrate your Node runtime declarations.

The git error "Fatal: refusing to merge unrelated histories" occurs when a user action, such as git merge, can cause the rewriting of history data. It is git's way to ensure the user fully understands the result of their action. Read on how to solve this error.

The git error "Fatal: not a git repository" occurs when you attempt to run a git command but weren't inside a git repository. Read this article for ways to solve this error.

The git error "Remote origin already exists" occurs when you attempt to create a link to a remote repository called origin but a remote with that name is already configured. Read this article on how to fix it.

Our secret pub crawl party during AWS Re:Invent conference in Vegas

Last Friday a security breach involving git repositories was reported. Hackers broke into private repos across GitHub, GitLab, and Bitbucket, wiped them, and asking the

Developers spend a lot of time working with git and GitHub, so investing in improving your GitHub practices makes a lot of sense. Implementing best practices in this guide could help the team improve developer productivity and reduce security risks.

10 most useful git commands guide: the intuitive and actual commands for common git tasks like renaming a branch, removing files, and undoing changes, and more.

Best practices for writing git commit messages - cheatsheet included. Read how to optimize git commit messages to improve your development productivity.