clearlydefined / clearlydefined/service
Include release version information from github
- Dominant language
- TypeScript
- Stars
- 51
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
Currently github information associated with a component does not provide the release version information of that item.
This is becoming a rather pattern to perform versioning and releases within github itself, which is usually tag based. For example [log4j](https://github.com/apache/log4j/releases)
An approach would be to use the [release api](https://developer.github.com/v3/repos/releases/) for every repository being scanned and store the version information beside the commit hash.
It would be very helpful to be able to lookup source code in github using components name and version in that fashion.
Please let me know if this is something worth considering and pursuing.
Basem Vaseghi , Daimler TSS GmbH, [Impressum](https://github.com/Daimler/daimler-foss/blob/master/LEGAL_IMPRINT.md)
Contributor guide
Research direction
No files, tests, or entry points are named. Start by tracing how GitHub component data and commit hashes are scanned and stored, then review the linked GitHub Releases API documentation. Done should include release version information alongside the commit hash and support lookup by component name and version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- api, backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100