Use github hooks to start building rakudo as soon as there's a new commit
Nobody has claimed this yet.
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
18:13:36 <Geth> ¦ rakudo: 9e6ae276a9 | (Zoffix Znet)++ | src/core/operators.pm6
18:13:36 <Geth> ¦ rakudo: Do not sink taken values in SEQUENCE
…
18:16:48 <Zoffix> e:say (<a b c>, *.reverse ... *)[5]
18:16:48 <evalable6> Zoffix, rakudo-moar 057966987: OUTPUT: «(exit code 1) The iterator of this Seq is already in use/consumed by another Seq(you migh…»
18:16:55 <Zoffix> 🤬🤬🤬🤬🤬
…
18:18:41 <Zoffix> e:say (<a b c>, *.reverse ... *)[5]
18:18:41 <evalable6> Zoffix, rakudo-moar 9e6ae276a: OUTPUT: «(c b a)»
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 by investigating the repository's GitHub hook and build automation setup; the issue does not name any files, tests, or entry points. Done means a new Rakudo commit automatically starts a build through the GitHub hook.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100