GitHub Actions and Shipa Webinar

As a software engineer, leveraging GitHub is one of those tools that transcend your personal and professional development activities. Bringing open source to the masses, GitHub is a familiar platform for many. A newer addition to the GitHub Platform is GitHub Actions which was originally a workflow engine, now expanding into CI/CD. Combining the ubiquity of GitHub Actions to your GitHub project/repository with the powerful application abstractions that Shipa provides is a great developer experience. Watch this webinar recording combining the power of the two platforms.

How GitHub's protocol changes impact your Puppet code deployments

GitHub is in the process of improving Git protocol security by removing insecure DSA keys and legacy ciphers, updating requirements on RSA keys, and adding more secure key signature algorithms ECDSA and ED25519. On January 11, GitHub ran a planned brownout event day to shake out affected clients. Our team at Puppet discovered that many users of Code Manager and r10k were affected by this change.

Use Datadog's GitHub and source code integrations to streamline troubleshooting

GitHub Apps is a service that helps you automate key processes in your workflow. Datadog now uses GitHub Apps to interact directly with the GitHub API, enabling you to add valuable context to your notebooks. And once you’ve also integrated Datadog with your source code, you can access links to Git repositories and inline code snippets for stack traces.

Trigger your CircleCI pipelines from a GitHub Actions workflow

If you are already a GitHub user, you may know that GitHub Actions provides you with powerful tools to increase efficiencies in your software delivery life cycle. Actions can be impactful for team collaborations and process simplification. For example, you can automate things like building a container, welcoming new users to your open source projects, managing branches, or triaging issues.

Git Integration for Jira v4.0 - New Git Indexing

Zip into Git Integration for Jira version 4.0! Our team has been whipping up some speedy new features and improvements to enhance your Git Integration for Jira Data Center and Jira Server experience. Do more in Git without leaving Jira, reducing context switching for a better workflow. Start using Git Integration for Jira free today! Start Free Trial

GitKraken Client v8.2 - New Workspaces & Themes

We’re excited to share what’s new and improved in the v8.2 release of GitKraken Client. Even solo superheroes will benefit from Workspaces but we’ve made a lot of updates designed for Teams to get the most out of Git. So assemble your team and get ready to tackle even the largest projects in Git. Keep reading this article or watch the video below to see what’s new! We just can’t stop improving productivity with Git.

A Major Moment in GitKraken's Journey

Before I introduce myself, I first want to highlight a monumental day in our company’s story. Today, we begin writing a new chapter under a new company name. We’ve decided to name the entire company after our flagship product, the ultra-popular GitKraken Client. Why make this move now? It’s much more than a cosmetic name change. Today ushers in the next phase in our evolution – one in which we will become the premier provider of Git tools for developers around the world.

Git vs GitHub

For my students, one of the first services we add to their toolbelts is GitHub, a place where they can “publish code and collaborate.” Students also benefit from using the GitKraken Client, which has proven to be a fantastic way of enabling students to engage in a workflow and familiarize themselves with the vocabulary of version control with Git. At some point, however, students confound GitHub vs Git, often thinking they are tightly related, or even the same thing.

Recovering from the Git detached HEAD state

The introduction of Git as a source-code management system in 2005 fundamentally transformed the process of software development. Git allows developers to maintain a history of changes, or commits, to their code and revert to previous commits in seconds if something goes wrong. It makes collaboration easier by allowing branching to keep code for different features separate and seamlessly merging commits by various people.