Adalennis opened a new issue, #9490: URL: https://github.com/apache/hop/issues/9490
### What needs to happen? Follow-up to the comment on #9395: some areas with their own plugins and docs have no component in the issue forms, so issues about them end up under CLI, Transforms or Other. Proposed new components: | Component | Code | |---|---| | AI | `plugins/tech/ai`, `plugins/transforms/languagemodelchat`, `plugins/transforms/textchunker` | | Git | `plugins/misc/git`, `plugins/tech/git-vfs` | | Lineage | `plugins/tech/openlineage` | | Lint | `plugins/misc/lint` | | Spark | `plugins/engines/spark` (the native engine, not the Beam Spark runner) | | Unit Testing | `plugins/misc/testing` | Rename "Neo4j" to "Graph Databases". The graph plugins now cover Neo4j, Memgraph, Amazon Neptune, FalkorDB, Apache AGE, Gremlin Server and JanusGraph (`plugins/tech/neo4j`, `age`, `falkordb`, `gremlin`), and the docs group them under Graph Databases. Renaming the existing `Neo4j` label keeps it on the issues that already have it, and the `pr-rules.yml` entry should then cover all four plugin folders. Changes: - `.github/ISSUE_TEMPLATE/bug.yml`, `feature.yml` and `task.yml`: add "Component: <name>" for the new components to the Issue Component dropdown, in alphabetical order, and rename "Component: Neo4j" to "Component: Graph Databases". - `.github/issue-rules.yml`: one rule per new component, so `tag-ur-it` adds the label, and the Neo4j rule changed to Graph Databases. - `.github/pr-rules.yml`: the Graph Databases entry covering the four graph plugin folders, and optionally globs for the new labels so `actions/labeler` tags PRs that touch these modules. - Labels (needs a committer): create AI, Git, Lineage, Lint, Spark and Unit Testing, and rename Neo4j to Graph Databases. The existing `Logging` label has no component in the forms either. It could be added at the same time. ### Issue Priority Priority: 3 ### Issue Component Component: Other -- 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]
