This follows recent updates to support Bolt app development with the Slack CLI v3.0.0 release, and aligns with how we share our other frameworks, packages, and SDKs.

Developing in public

Tooling that developers use often comes with an expectation of being open source.

Having source code available to review and modify as needed isn’t just convenient for those interested. It can help build trust through open dialog and transparent changes.

A forum for direct feedback on ongoing changes is so beneficial to the growth of projects with these conversations influencing the direction of a roadmap and the priorities of our team. Bug fixes can find resolution sooner and unknown use cases are uncovered often in issues submitted.

We’ll also be quick to admit that nerves from making a mistake on the internet can be a real concern when working on open source, but we find these moments lead to great learnings and connections and better tooling all around.

Community contributions

Part of our excitement in this announcement is around sharing back to the kind Golang community as well.

We rely so much on open source packages and modules to build the tools we share and hope to contribute back whenever possible, whether this be in upstream fixes and improvements or regular community encouragement.

When building the Slack CLI, the reduced barriers to contribution in a compiled language made Go a great choice for us and we hope this might be extended to the reader!

Compiling the code

While our guides for getting started offer a quick path to start developing a Slack app, editing the source code might be interesting for the curious hackers and tinkerers alike.

Check out the latest changes in a development setup of your own with the following commands:

$ git clone https://github.com/slackapi/slack-cli
$ cd slack-cli
$ make build

And for those wanting to make a contribution, whether a small fix or feature addition otherwise, the CONTRIBUTING.md and MAINTAINERS_GUIDE.md files were written for you!