FOSSA pre-merge check
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
Research direction
Start by locating the existing post-merge FOSSA checks that work on main and identify the shared workflow entry point used for pull requests. Define how the check exposes results in each PR, blocks merging for problematic licenses, and permits explicit exceptions for multi-licensed packages.
Written by the indexing model from the issue text.
Description
In otel-demo, we have missed that k6 package brings problematic license in https://github.com/open-telemetry/opentelemetry-demo/pull/3564
All FOSSA checks now are post-merge and working on main.
It will be great to have shared check which will be executed on every PR. It not necessary to report results to FOSSA, results should be available in the PR.
I suppose that we need a way to ignore some issues (for multi-licensed packages), but in general, it should block merge.
- Dominant language
- JavaScript
- Stars
- 7
- Forks
- 23
- Avg merge
- 15h 46m
- Merged PRs (30d)
- 41
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 open-telemetry/shared-workflows
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
open-telemetry/shared-workflows#532 · 1 comment ·
Maintainers usually reply within 1 day
-
Hash-lock pull request dashboard Python dependencies (move to uv)Possibly taken @irfadkp claimed this 3 days ago. Opendashboard dependencies
Difficulty 4/5 3-5 days Newbie friendliness 51/100
open-telemetry/shared-workflows#517 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
open-telemetry/shared-workflows#492 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
open-telemetry/shared-workflows#422 ·
Maintainers usually reply within 1 day
-
Support Zizmor SARIF uploads from private repositoriesMay be free again @trask claimed this 61 days ago, and no pull request is open. Open
open-telemetry/shared-workflows#390 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in open-telemetry/shared-workflows
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
manuXD270516/descanso#80 ·
Maintainers usually reply within 2 days
-
feat: Warn while typing a forbidden character in a file namePossibly taken @Mittalnew claimed this today. Openapp Drive 📁 enhancement OO Docs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
linagora/twake-drive#4620 · 1 comment ·
Maintainers usually reply within 1 day
-
国战吕蒙【谋断】问题Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Edit: Hello TasteOpenchannels:edit check:passed
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day