ewega opened a new issue, #8685:
URL: https://github.com/apache/incubator-devlake/issues/8685

   ## Goal
   Standardize the plugin identifier/name as `gh-copilot` (instead of 
`copilot`) across backend + config-ui, so the plugin is discoverable/consistent 
and aligns with the folder name `backend/plugins/gh-copilot`.
   
   ## Why
   - Avoid confusion/collisions with any future generic “copilot” naming.
   - Ensure UI plugin registry resolves the plugin config by the correct name.
   
   ## Scope
   - Backend plugin `Name()` and all backend references that key off plugin 
name (API routes, blueprint/pipeline plugin name, connection helper usage).
   - Config-UI plugin registry key/name so it matches backend.
   - Update docs/tests/fixtures that reference the plugin name.
   
   ## Non-goals
   - No functional changes to data collection beyond name/identity updates.
   
   ## Acceptance Criteria
   - Backend reports plugin as `gh-copilot` in the plugins list endpoint.
   - Connections API routes for this plugin use `gh-copilot`.
   - Config-UI shows the plugin using the `gh-copilot` key (no placeholder 
fallback due to unknown plugin name).
   - Unit/e2e tests (where applicable) pass.
   
   ## Compatibility Notes
   If backward compatibility is required, add an alias/redirect so existing 
pipelines/connections referencing `copilot` continue to work, or provide a 
migration note if breaking change is acceptable.
   
   ## Implementation Notes (starting points)
   - Update `Name()` in backend plugin entrypoint: 
`backend/plugins/gh-copilot/impl/impl.go`.
   - Search/replace references to `copilot` used as the plugin key across 
backend + config-ui.


-- 
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]

Reply via email to