“releases” shortcut knows about tags that are not built yet
Nobody has claimed this yet.
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
https://irclog.perlgeek.de/perl6/2017-04-23#i_14472538
And here is why it happens: https://github.com/perl6/whateverable/blob/f1f8840807179c64f9e4884fa28e3fe0699a0c10/build.p6#L68-L72
In short, 2017.04.3 was tagged before it was merged into nom, so committable got to know the tag before it was actually built.
In the source (see link above), we have two separate lines for building everything on nom and for building all existing tags. However, it wasn't working for some reason, so it was commented out and we no longer build tags (we don't really need to because all old tags were built already).
Alternatively, we can do #117 and it will make this problem irrelevant.
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 build.p6 around lines 68-72 and review how the separate nom and existing-tag build steps relate to the releases shortcut. Check issue #117 before choosing an approach; done means releases no longer exposes tags before they have been built.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100