Testing Validate Command after #273 merged

[Atharva-Shinde]

Provide the actual tweet content between the commented colons

This is a test TweetThis is a test Tweet

#274 (comment)

[Atharva-Shinde]

the job was skipped for some reason

[Atharva-Shinde]

/validate
EDIT: validating for This is a test Tweet

[github-actions]

A new file has been created with your tweet content. Please refer the below linked PR

[Atharva-Shinde]

worked! now with exceeding char limit tweet

[Atharva-Shinde]

/validate
EDIT: validating for
This is a test TweetThis is a test TweetThis is a test TweetThis is a test TweetThis is a test TweetThis is a test TweetThis is a test TweetThis is a test TweetThis is a test TweetThis is a test TweetThis is a test TweetThis is a test TweetThis is a test TweetThis is a test TweetThis is a test TweetThis is a test TweetThis is a test TweetThis is a test Tweet

[github-actions]

Tweet content length is exceeding the permitted tweet length. Please rephrase the tweet and comment /validate to trigger the workflow again.

[Atharva-Shinde]

great!
now changing back and validating

[Atharva-Shinde]

/validate

[github-actions]

A new file has been created with your tweet content. Please refer the below linked PR

[Atharva-Shinde]

/validate
EDIT: validating for This is a test TweetThis is a test Tweet

[github-actions]

A new file has been created with your tweet content. Please refer the below linked PR

[Atharva-Shinde]

/validate
EDIT: validating again for This is a test TweetThis is a test Tweet

[github-actions]

A new file has been created with your tweet content. Please refer the below linked PR

[Atharva-Shinde]

I cross-checked on my fork and wanted to re-surface it here.

1. With Fix Validate command #273 merged, now a tweet PR isn't automatically generated unless we /validate on an issue
2. It's still not working as expected on this repo.
3. But is totally working on my fork. Always.
   ref: with changes of #273:- here
   without changes of #273:- here

[chris-short]

@Atharva-Shinde We should probably setup some time to look into this together. More eyes are better usually. With KubeCon upon us, this week and next are pretty much toast (unless you're going to be in town).

[Atharva-Shinde]

I Agree @chris-short ! Just wanted to get the ball rolling as it's been hanging around for a long time now. IMO this Issue could be the test issue to test our workflow so that there's no need to wait for creating new tweet issue every time we want to test the workflow. I've also setup an issue so that we can keep track of this in one place.
Although I'm in full support of closing this issue if it's just getting redundant by time and isn't adding any value.

Feedbacks welcome :)

[imnmo]

@chris-short @Atharva-Shinde this merge didn't solve the problem and I see new file changes after the merge. See here: https://github.com/kubernetes-sigs/contributor-tweets/pull/281/files

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[imnmo]

/close

see here #289

[k8s-ci-robot]

@imnmo: Closing this issue.

In response to this:

/close

see here #289

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.