Open heitorlessa opened 1 month ago
Caveat. E2E test might be a problem as token might be scoped to current repository only.
To prevent a complex seed data for issues and pull requests, E2E is sourcing data from a known repository and using this repository to create/update reports.
I'll probably tackle this in 2 separate PRs: one for linting & code quality and another for E2E.
If we need to create a GH PAT, we could consider using @aws-powertools-bot and give it access to that other known repo.
As of now, we're not running linting and tests as part of CI for this repo. They do run locally and have E2E tests too.