TOGEP opened a new pull request, #831:
URL: https://github.com/apache/devlake-website/pull/831
# Summary
Update the CircleCI configuration docs to recommend creating a CircleCI
Personal API Token for DevLake, link to CircleCI's official SSO guidance for
Personal API Tokens, and mention that DevLake can only detect CircleCI projects
followed by the token owner.
### Does this close any open issues?
No related open issue found.
### Screenshots
N/A
### Other Information
Investigation notes:
- DevLake's CircleCI connector sends the configured token with the
`Circle-Token` header and uses CircleCI API v2 endpoints for connection and
data collection, including `/v2/me`, `/v2/me/collaborations`,
`/v2/project/{slug}`, `/v2/project/{slug}/pipeline`,
`/v2/pipeline/{id}/workflow`, `/v2/workflow/{id}`, and `/v2/workflow/{id}/job`.
- CircleCI's API token documentation describes Personal API Tokens for API
v2 usage, while Project API Tokens are documented for API v1 project access.
- DevLake project discovery reads followed projects from CircleCI, so users
need to follow projects in CircleCI before they appear in DevLake.
Validation:
- `git diff --check main...HEAD`
- `npm run build`
- `npm run serve -- --host 127.0.0.1 --port 3000` was started, but did not
begin listening on port 3000 within the wait window and was stopped.
--
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]
