jaegertracing/jaeger

Improve FOSSA integration

Open

#2,432 opened on Aug 29, 2020

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (2,326 forks)batch import
help wanted

Repository metrics

Stars
 (18,974 stars)
PR merge metrics
 (Avg merge 4d 11h) (85 merged PRs in 30d)

Description

Related to FOSSA scanning introduced in #2347

  • make the check go red when license violations are discovered
  • make the scan report easily accessible, e.g. by clicking on the Details next to the check, and/or posting a summary as a PR comment

Contributor guide

Research direction
Understand the current FOSSA integration in the repository. Look at the GitHub Actions workflow file (likely .github/workflows/fossa.yml) and the FOSSA documentation for GitHub Checks. Modify the workflow to fail on license violations and post a summary comment on the PR.
Tech stack
gogithub actions
Domain
backendci cd
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60