Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Pins don't work in slackbot or direct message channels

Open
#148 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
api

Research direction

Start from the pins_add entry point and reproduce the request for #general, @username, and the returned channel ID. Compare these cases with Slack's pinning API requirements; done means establishing whether the behavior is expected or identifying a client defect and a regression test scope.

Written by the indexing model from the issue text.

Description

bug?

Using the ruby api if it makes a difference
After posting a message:
I can pin a message in the #general channel
client.pins_add(channel:"#general", timestamp:_["ts"])
When I try to do the same in a personal or slackbot channel:

client.pins_add(channel:"@username", timestamp:ts)

or taking the channel code from the response from chat_postMessage
client.pins_add(channel:"E13R30LAG", timestamp:ts)

It fails with "channel not found"

Is this expected behaviour or am I doing something silly?

Dominant language
Ruby
Stars
1.3k
Forks
222
Avg merge
1d 14h
Merged PRs (30d)
3

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 slack-ruby/slack-ruby-client

All issues in slack-ruby/slack-ruby-client

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.