Raku / Raku/whateverable

Understand :m

Open
#249 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ANNOYINg evalable
Dominant language
Raku
Stars
19
Forks
16
PR merge metrics
No merged PRs in 30d

Description

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.

Research direction

Start with the linked IRC log to determine what :m refers to and what behavior or explanation is expected. No source files or tests are named, so identify the relevant bot entry point or documentation location before defining what completion should look like.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.