Releasable is too strict
Open
Nobody has claimed this yet.
good first issue
hacktoberfest
releasable
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
<jnthn> releasable6: when is the next release, kind bot?
<releasable6> jnthn, I cannot recognize this command. See wiki for some examples: https://github.com/perl6/whateverable/wiki/Releasable
It should give the right answer as long as “next” or “when” is in the message.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the releasable6 command and the examples in the linked Releasable wiki page. Trace how messages containing “next” or “when” are recognized and verify the example request in the issue. Done means that request returns the next release information instead of an unrecognized-command response.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100