What is the best way for a team to collaborate on a slack bolt app?

Open
#343 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
cli, developer-experience

Research direction

Start with the proposed get-started README and the Slack CLI app-manifest workflow described in the issue. Document a reproducible setup for another developer and clarify whether the CLI can support a shared sandbox environment; no specific source files or tests are identified.

Written by the indexing model from the issue text.

Description

docs question
Question

Hello, I'm currently working on a slack app using boltjs (multiworkspace and http events, not in socket mode), I did not use slack cli or started from a template. I'm in the process of making a get started readme that would allow another developper to get the app up and running quickly. So far it seemed to require creating the app from manifest on slack dev dashboard. I then took a dive into slack cli and I'm trying to see if it could accelerate the dev workflow, the two biggest things I'm trying to improve are:

  1. Allowing a dev to get the app running as quickly as possible on his machine
  2. Possibly setting up a sandbox environment

Thanks for your help

Version

3.12

OS Info

Please paste the output from:

ProductName: macOS
ProductVersion: 15.5
BuildVersion: 24F74
Darwin Kernel Version 24.5.0: Tue Apr 22 19:53:27 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6041

Steps to reproduce:
Expected result:
Actual result:
Requirements
  • I've read and understood the Contributing guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've searched for any related issues and avoided creating a duplicate issue.
Dominant language
Go
Stars
305
Forks
46
Avg merge
1d 11h
Merged PRs (30d)
23

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from slackapi/slack-cli

All issues in slackapi/slack-cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.