Create 07-05-2021-first-tweet.tweet

[rainleander]

No description provided.

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[k8s-ci-robot]

Welcome @rainleander!

It looks like this is your first PR to kubernetes-sigs/contributor-tweets 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/contributor-tweets has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[rainleander]

/check-cla

[rainleander]

This tweet may not be relevant anymore... Can I help moderate these pulls?

[mbbroberg]

LOVE this! Wdyt @kaslin?

[mbbroberg]

Hey @rainleander, we'd love to get your involvement here. @kaslin is lead and we could talk you coming in as shadow or another contributor in general.

[rainleander]

Hey @rainleander, we'd love to get your involvement here. @kaslin is lead and we could talk you coming in as shadow or another contributor in general.

Definitely; I'm comfortable doing either!

[kaslin]

Ah yeah, I'm so sorry I missed this back when you submitted it! KubeCon threw me off. But yes, I love it! I'm tempted to just go ahead and send it anyway. I can add a reply on it with more context.

[rainleander]

Yeah, it's a tornado. Definitely reply to add context once it goes through. I can do the same!

[kaslin]

Sorry about the additional delay on this, we're definitely learning some about our processes here! We just introduced some new automation to the repo which broke things for a minute, so this tweet will serve an additional purpose as a test in the process of our automation updates!

Thank you, @rainleander for unintentionally becoming the first member of our automation testing team! XD (This is a joke about the testing team, but really thank you! This PR makes me so happy.)

[rainleander]

No worries at all; let's get it all going smoothly!

[rajula96reddy]

Hey @rainleander Thanks for being patient. The workflow should be fixed now. Can you try rebasing this PR on the latest master branch? Thanks!

[rainleander]

Hey @rainleander Thanks for being patient. The workflow should be fixed now. Do you rebasing this PR on the latest master branch? Thanks!

Done!

[rajula96reddy]

Hey @rainleander Thanks for being patient. The workflow should be fixed now. Do you rebasing this PR on the latest master branch? Thanks!

Done!

Correct me if I am wrong, I don't see the rebase changes. Can you check again?
https://github.com/rainleander/contributor-tweets/tree/patch-1 still says "This branch is 1 commit ahead, 13 commits behind kubernetes-sigs:master. "

[rainleander]

Weird. Did it again?

[rajula96reddy]

Weird. Did it again?

I can the new changes now. The workflow is working. The tweet will go out once we merge this.

Just an FYI for future purposes: It is advised to not do a merge rebase if possible, it creates an additional commit. A normal rebase is preferred.

[kaslin]

/approve /lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kaslin, rainleander

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [kaslin]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kaslin]

/lgtm