You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following up on #1400, one of our first PRs in the new repo is a larger donation of Splunk Android code. This PR was intentionally created with full commit history enabled in order to preserve and respect all the prior work of contributors.
Unfortunately the PR is hung up on EasyCLA and has been in this state for a week now:
We have tried the /easycla trick multiple times and I have tried closing/reopening, all with no luck.
I understand that @trask opened a ticket with them to check on this and that they indicated that EasyCLA sometimes struggles with PRs with more than 50+ commits. 🙃
So we're looking for help moving this forward. We think one possibility is to temporarily disable EasyCLA on the repo just long enough to get the first code commit in, and then turn it back on. I (as an otel-android maintainer) don't have permission to do this. Open to other ideas.
Thanks!
The text was updated successfully, but these errors were encountered:
Following up on #1400, one of our first PRs in the new repo is a larger donation of Splunk Android code. This PR was intentionally created with full commit history enabled in order to preserve and respect all the prior work of contributors.
Unfortunately the PR is hung up on EasyCLA and has been in this state for a week now:
We have tried the
/easycla
trick multiple times and I have tried closing/reopening, all with no luck.I understand that @trask opened a ticket with them to check on this and that they indicated that EasyCLA sometimes struggles with PRs with more than 50+ commits. 🙃
So we're looking for help moving this forward. We think one possibility is to temporarily disable EasyCLA on the repo just long enough to get the first code commit in, and then turn it back on. I (as an otel-android maintainer) don't have permission to do this. Open to other ideas.
Thanks!
The text was updated successfully, but these errors were encountered: