Use Case
We were facing issues with CircleCI similar to #132 and also you need authorized user commit to get workflow running in the first place. We did analysis of GHA vs CircleCI and GHA seemed to be better overall option for Hypertrace CI use-case.
We have already done POC on attribute service repo: https://github.com/hypertrace/attribute-service and we should move rest of the repos to use GitHub actions as well.
Proposal
We have created template workflows which you can import for each repo and modify according to requirements (similar to this: https://github.com/hypertrace/attribute-service/actions/new).
This issue will track migration to GitHub Actions:
Use Case
We were facing issues with CircleCI similar to #132 and also you need authorized user commit to get workflow running in the first place. We did analysis of GHA vs CircleCI and GHA seemed to be better overall option for Hypertrace CI use-case.
We have already done POC on attribute service repo: https://github.com/hypertrace/attribute-service and we should move rest of the repos to use GitHub actions as well.
Proposal
We have created template workflows which you can import for each repo and modify according to requirements (similar to this: https://github.com/hypertrace/attribute-service/actions/new).
This issue will track migration to GitHub Actions: