Skip to content

Conversation

@dd-jy
Copy link
Contributor

@dd-jy dd-jy commented May 17, 2023

Description

Add to correct with sbom-info.yaml

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Documentation update
  • Refactoring, Maintenance
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Signed-off-by: Jiyeong Seok <jiyeong.seok@lge.com>
@dd-jy dd-jy added the enhancement [PR/Issue] New feature or request label May 17, 2023
@dd-jy dd-jy requested a review from soimkim May 17, 2023 09:30
@dd-jy dd-jy self-assigned this May 17, 2023
@dd-jy dd-jy merged commit 65011fe into main May 19, 2023
@dd-jy dd-jy deleted the sbom_merge branch May 19, 2023 05:36
-c <core>\t\t Select the number of cores to be scanned with ScanCode."""
-c <core>\t\t Select the number of cores to be scanned with ScanCode.
--no_correction\t Enter if you don't want to correct OSS information with sbom-info.yaml
--correct_fpath\t Path to the sbom-info.yaml file"""
Copy link
Contributor

@soimkim soimkim May 25, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dd-jy , --correct_fpath <path>\t 로 변경 필요해보입니다.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@soimkim
변경 필요한 사유가 있을까요? help 메시지 정렬과 동작에 이상 없어보여 문의드립니다.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<path> 를 입력하면 깃헙에서 뭔가 tag인지 안보이네요

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#122 에 수정하였습니다~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement [PR/Issue] New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants