JoaoManierii opened a new issue, #8541:
URL: https://github.com/apache/incubator-devlake/issues/8541
<!-- Clarification on GitHub Releases dataflow: `_tool_github_releases` not
mapped to a domain table / missing contributor-related fields -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
## Question
We’re ingesting GitHub **Releases** with the GitHub plugin and we can see
data landing in the table `_tool_github_releases`. However, we don’t see any
corresponding **domain-layer** table populated for releases (e.g., a `releases`
table or similar), and we’re missing some fields we expected such as
**contributors** (or contributor/author-related info aggregated per release).
Questions:
1. Is there an existing domain mapping / conversion step that should move
data from `_tool_github_releases` into a domain-layer table?
- If yes, which subtask(s) / plugin should we enable in the Blueprint to
populate it?
- If no, is this by design and should we query `_tool_github_releases`
directly for analytics?
2. For **contributor-related** information on releases:
- Is there a supported way (built-in column, relationship, or enrichment
step) to attach contributors/commit authors to a given release?
- Do we need to enable a specific plugin or subtask (e.g., GraphQL or
another enrichment) to get contributor counts or lists per release?
- If this is not available out-of-the-box, is there a recommended
approach to derive contributors for a release (e.g., via tags, commits between
release tags, etc.)?
3. If a newer DevLake version adds a proper domain table or additional
release fields, please let us know from which version this is available and
what migration/Blueprint changes are required.
## Screenshots
- Screenshot of `_tool_github_releases` showing current columns.
<img width="1199" height="748" alt="Image"
src="https://github.com/user-attachments/assets/00cc4cb9-03f4-45ac-9e2e-9ba6eaf0afeb";
/>
## Additional context
**Environment (placeholders):**
- DevLake version: `1.0.1@e061ef2`
- Database: MySQL `8.0.26-google`
Any guidance on the expected dataflow, required subtasks, or **version
upgrades** would be appreciated. Thank you!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
