With the recent announcement of the update to GitHub Actions, we are excited to announce support for GitHub Actions in both the GitKraken Git GUI and GitKraken Boards for task tracking.
If you haven’t seen it yet, here is the GitHub announcement about the GitHub Actions update:
What is GitHub Actions?
GitHub Actions is a cloud service that you can use to automatically build and test your code projects and make it available to other users. It works with just about any language or project type.
GitHub Actions combines continuous integration and continuous delivery (CI/CD) to constantly and consistently test and build your code and ship it to any target.
See how continuous integration and delivery (CI/CD) fit into the DevOps lifecycle.
You can also use Actions from the GitHub Actions Marketplace to create automation and workflows to perform virtually any action based on various triggers.
In the rest of this blog post, we’ll explain how the GitKraken Git GUI and GitKraken Boards are supporting GitHub Actions.
Create and Manage GitHub Action Workflows
Workflows in the GitHub Actions service run actions that build, test, and deploy your code. They exist as
.yml files inside the
.github/workflows directory in your repository. The GitHub Actions integration helps you easily create and manage these workflow files right inside the GitKraken Git GUI.
A new GitHub Actions section has been added to the left panel in the GitKraken Git GUI that will be displayed for repositories with an upstream remote on GitHub, or when a repository contains the
.github/workflows directory. This section will display any existing workflow files on the currently-checked-out branch of your repository, and provides quick access to view and edit those files with GitKraken’s built-in editor.
You can create a new workflow in the GitKraken Git GUI by clicking the green Create Workflow button.
From here, you can select an optional template, or start your own workflow from scratch.
Newly-created workflow files will immediately open in GitKraken’s file editor where you can review, modify, and save changes. Simply stage the workflow file in the commit panel, and commit to see it appear along with the other workflows in the left panel.
Push your changes to GitHub and your new workflow is ready to be used by the GitHub Actions service!
GitKraken Boards Support
Automate Card Updates
We are excited to announce the immediate availability of GitHub Actions for GitKraken Boards. You can now automate the manipulation of cards on your GitKraken Boards using GitHub Actions. We have initially released six GitHub Actions for you to use in your repository workflows. For a full list of Actions and more information, refer to https://github.com/Axosoft/glo-actions/. For now, the example below can get you started.
Example: Move linked cards to the Deployed column when a PR is merged on GitHub.
Create a Personal Access Token (PAT) in your GitKraken account. Actions will need read/write access only.
*Note: All actions taken by this user will automatically update the cards in Glo.
2. Add the Access Token for the PAT as the value for a secret in your repository settings on GitHub.
3. Set up a workflow for your repository on GitHub that will trigger the necessary Actions (you will add the secret name as the
4. Add a link to your card in your PR description.
That’s it! The Actions will now automatically update the linked card from your Pull Request.