Update generate metadata #56
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pramit-d
pushed a commit
that referenced
this pull request
Feb 9, 2024
* Update generate metadata (#56) * Fixed metadata generate issue for Be-Secure origin projects * Updated dev-kit according to the new besecure-asset-store path * Fixed bug: generate criticality_score (#58) * Fixed code for criticality score * removed discontinued version of criticality_score * Update README.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed [Bug]: Unable to generate metadata for BLIman #55
Root cause: BeS-dev-kit was showing errors while the user tried to generate metadata for Be-Secure original/own projects (like. BLIman, BeS-dev-kit, BeSLighthouse, BeSman, etc). For these types of projects, there are no parent details available in GitHub API. BeS-dev-kit trying to fetch parent details at the time of metadata generation. For this reason, the user is getting an error.
Resolution: If parent is available in the above-mentioned GitHub API, BeS-dev-kit will fetch the data. Otherwise, it will skip the process.
Added new besecure-asset-store repository Update metadata file location #54
Removed besecure-osspoi-datastore and added besecure-asset-store repository.