Repository navigation
Triage request: AshwinUgale #7478
Replies: 5 comments 2 replies
|
approved |
|
@AshwinUgale I revoked your access to our triage role after an internal audit. This is due to no fault of your own and I will reply back to you here once this is resolved. We apologize for the inconvenience and really do appreciate your contributions! |
|
Hey @AshwinUgale, sorry it’s taken me this long to get back to you. Three weeks is too long to leave you without an update. I also wanted to say that I’ve seen you continuing to contribute, including the mutation-testing experiment and your recent comparison of the functional-test suites. I really appreciate the time and thought you’re putting into this, especially while you’ve been waiting on us. Thanks for your patience and for continuing to help improve Fullsend. |
|
Hello @ascerra ,Thanks for the update, no worries on the timing, and no rush on the CI permissions, I'll keep contributing in the meantime. |
|
Hey @AshwinUgale, you now have triage access to fullsend, agents, and experiments repos! Sorry it took us this long to get this sorted. I really appreciate your patience and that you’ve continued contributing while waiting. Your work on evals, telemetry, and the testing experiments has been valuable, and I’m glad we can finally get this moving for you. I’m closing this request now that access is in place. Thanks again for the time and care you’re putting into Fullsend! |
Uh oh!
There was an error while loading. Please reload this page.
Contribution history
#7454
#7386
#5999
fullsend-ai/experiments#39
Why do you need triage access?
I want to keep working on the evals and telemetry area, I want to extend more on the current EM-002 scorer issue I raised , triage access will be nice to have so I can run it on my issues myself instead of waiting for a maintainer to do it,
Checklist
All reactions