FOSSA pre-merge check

Open
#226 0 comments 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Domain
ci-cd, security

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-telemetry/shared-workflows

All issues in open-telemetry/shared-workflows

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.