Overview

Codelingo is a Platform as a Service (PaaS) for software development teams to solve software development problems. It treats your software as data and automates your workflows, called Actions, with the rules and patterns you define, called Specs.

Our flagship Action is the Review Action, which checks a repository's pull requests conform to its project specific patterns. We have also built the Rewrite Action and the Docs Action.

Quick Starts

Playground

Test out writing a Spec and running a Action online with zero installs using the CodeLingo playground - it's easier than you think!

Dashboard

The CodeLingo Dashboard lets you manage you automated workflows for each of your repositories. It is your hub for adding and removing Specs from your repositories and running Actions. Sign in with GitHub and follow the tutorial to run your first Action.

GitHub Review Action

After installing CodeLingo on GitHub, write the following codelingo.yaml to the root of your repository:

# codelingo.yaml file

specs:
  - import: codelingo/go

You're done! Every pull request to your repository will now be checked against the Go Spec Bundle we imported above like so.

Other Spec Bundles (including for other languages) from the community can be found at codelingo.io/specs.

Getting Started Guide

A step by step guide to getting started with Specs and Actions:

View the getting started guide

Concepts

The CodeLingo platform has two key concepts: Specs and Actions.

Specs

A Spec is an encoded project specific best practice used to guide development. A Spec can be used for: coding styles, performance tuning, security audits, debugging, avoiding gotchas, reducing complexity and churn, and more.

View the guide and docs for working with Specs

Explore published Specs

Actions

An Action is an automated development workflow that leverages Specs to do some task, for example automating code reviews. While a Spec lives next to your code in a codelingo.yaml file, it is inert until an Action uses it.

Note:

We have deprecated flows in favor of actions. Please modify your codelingo.yaml files accordingly.

View the guide and docs for working with Actions