Conversation
|
Hi @KAZYPinkSaurus! Thanks for the contribution, and sorry I missed this when you first opened it. It looks like we made some changes to these files, would you mind merging Thanks! 🙇 |
|
Hi @KAZYPinkSaurus! It looks like we still need you to sign the CLA agreement before we can merge this. Would you mind checking the link in the comment from the CLAassistant? Thanks! 🙇 |
|
@heitortsergent |
|
@jdbaldry would you be able to help us here? Could the CLA not be updating because the PR was opened too long ago? 😖 |
|
@jdbaldry I tried the instructions to have the assistant run the check again, but it doesn't seem to be working. :( Should we try to close and open a new PR? |
|
I think it may be because there are two different authors in the commit log: https://github.com/grafana/k6-docs/pull/1685/commits |
|
If either you or @KAZYPinkSaurus can rewrite the history to remove that commit, perhaps by squashing all the rest together, then the CLA will pass. |
|
@KAZYPinkSaurus let me know if you can do what @jdbaldry suggested and squash the commits? I don't think I can do it since this is coming from your fork branch. :( |
|
Sorry to those accidentally added as initial reviewers. I performed a In case anyone is interested in the steps I took: |
|
Thank you so much @jdbaldry! 🙇 And thank you for your patience on this @KAZYPinkSaurus, sorry about the long wait. 🙇 |
* remove unsed receiver * fix * fix

What?
Remove unused receiver.
I hope this change helps you.
Checklist
npm startcommand locally and verified that the changes look good.docs/sources/nextfolder of the documentation.docs/sources/v{most_recent_release}folder of the documentation.docs/sources/nextfolder of the documentation.Related PR(s)/Issue(s)
nothing.