Skip to content

Conversation

@zimeg
Copy link
Member

@zimeg zimeg commented Nov 18, 2025

Summary

This PR updates the maintainer's guide with instructions to compile and install packages and documentation for local development! 📚

Requirements

@zimeg zimeg self-assigned this Nov 18, 2025
@zimeg zimeg requested a review from a team as a code owner November 18, 2025 02:46
@zimeg zimeg added docs M-T: Documentation work only semver:patch labels Nov 18, 2025
@codecov
Copy link

codecov bot commented Nov 18, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.02%. Comparing base (dcda03d) to head (38d0c74).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2437   +/-   ##
=======================================
  Coverage   93.02%   93.02%           
=======================================
  Files          40       40           
  Lines       11127    11127           
  Branches      713      713           
=======================================
  Hits        10351    10351           
  Misses        764      764           
  Partials       12       12           
Flag Coverage Δ
cli-hooks 95.23% <ø> (ø)
cli-test 94.79% <ø> (ø)
oauth 77.39% <ø> (ø)
socket-mode 61.87% <ø> (ø)
web-api 98.08% <ø> (ø)
webhook 96.66% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Member Author

@zimeg zimeg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📬 A note to kind reviewers from before now!


We have included `launch.json` files that store configuration for `vscode` debugging in each package. This allows you to set breakpoints in test files and interactively debug. Open the project in `vscode` and navigate to the debug screen on the left sidebar. The icon for it looks like a little lock bug with an x inside. At the top in `vscode`, select the configuration to run and press the green play icon to start debugging. Alternatively, on mac, you can press `cmd + shift + d` to get to the debug screen and `F5` to start debugging. If you are using `vscode` debugging, don't forget to lint the source (`npm run lint`) manually.

### 🧰 Local Development
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👁️‍🗨️ note: Hoping to have similar reference as @slack/bolt reference:

🔗 https://github.com/slackapi/bolt-js/blob/main/.github/maintainers_guide.md#local-development

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🪬 praise: Thanks too to @srtaalej for suggesting these addition!

Copy link
Contributor

@WilliamBergamin WilliamBergamin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yessss

@zimeg
Copy link
Member Author

zimeg commented Nov 21, 2025

@WilliamBergamin I share celebration for perhaps more clear commands and kind reminders! 📚 ✨

@zimeg zimeg merged commit e2e1fa7 into main Nov 21, 2025
57 checks passed
@zimeg zimeg deleted the zimeg-docs-maintainer-steps branch November 21, 2025 21:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs M-T: Documentation work only semver:patch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants