Have Circleci hashes for all ROMS outputted as comments in PR
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- build-system, ci-cd
Research direction
Review PR #2174 and issue #2168 first to understand the expected hash behavior and required input. Then trace the repository's CircleCI and local-build paths; done means hashes for every ROM output are regenerated and posted as comments for each relevant pull-request commit.
Written by the indexing model from the issue text.
Description
As title says.
With https://github.com/linuxboot/heads/pull/2174, hashes of PR should be always regenerated and valid. We need more input like https://github.com/linuxboot/heads/issues/2168 and for that to happen, local builds and CircleCI hashes need to be explicit for every commit.
- Dominant language
- Makefile
- Stars
- 1.6k
- Forks
- 211
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 6
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from linuxboot/heads
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
help wanted security SMM upstream
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oSoWoSo/vOid_Community_repOsitory#240 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
self-care self-care:docs-build-time-investigator
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-cao#15846 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 3 days
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
RedHatOfficial/aap-demo#211 ·
Maintainers usually reply within 1 day