Issue to PR automation seems to be broken

[rajula96reddy]

Our issue to PR automation seems to be broken after #104

We see the following error in the action log

   /usr/bin/git -c protocol.version=2 fetch --no-tags --progress --no-recurse-submodules --unshallow --force origin main:main
  fatal: couldn't find remote ref main
  Error: The process '/usr/bin/git' failed with exit code 128

We observed this in one of the recent issues #118

[k8s-ci-robot]

@chris-short: GitHub didn't allow me to assign the following users: me.

Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign me

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.

[chris-short]

/assign

[Atharva-Shinde]

We should change the name of contributor/tweets repository's default branch from 'master' to 'main'
I tried out in my local repository and it worked!

[chris-short]

This should be resolved. We'll need to tweet something to confirm though.

[Atharva-Shinde]

it worked! #124

[Debanitrkl]

Fixed
/close

[k8s-ci-robot]

@Debanitrkl: Closing this issue.

In response to this:

Fixed
/close

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.