Team, I saw this github.com/archestra-ai/archestra/issues/4416
Is this issue refearing to Google Agent 2 Agent protocol?
I was wonderig If I could make my first contribution to the community if this is about a2a protocol, since I've created about 3 / 4 projects with this protocol. Not interested in the bounty honestly, just interested in getting started and make a contribution to the community.
Diego Aguirre —
cc: @user @user ❤️
Matvey Kukuy (archestra team) —
Welcome!
Matvey Kukuy (archestra team) —
The issue looks good, and kindly asking not to tag team members without a specific need
Diego Aguirre —
Thank you Matvey, I will do, can I be assigned to that issue or I can attempt to solve it? I see Ildar Ishhkadov has it assigned.
Hi team — working on bounty #4468 (Anthropic Workload Identity Federation). CLA is signed and my PR is ready, but my contributor-onboard PR archestra-ai/archestra#4590 got a merge conflict on EXTERNAL_CONTRIBUTORS.md right after it opened. The merge-external-contributors workflow only triggers on PR open, so it's stuck. Could a maintainer rebase or reopen it so I get added to the allowlist? Then I can submit the WIF PR (already committed and tested locally). Thanks!
Is this issue refearing to Google Agent 2 Agent protocol?
I was wonderig If I could make my first contribution to the community if this is about a2a protocol, since I've created about 3 / 4 projects with this protocol. Not interested in the bounty honestly, just interested in getting started and make a contribution to the community.