Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update stale-community-issues.yaml #36990

Merged
merged 2 commits into from
Apr 11, 2024
Merged

Conversation

marcosmarxm
Copy link
Member

@marcosmarxm marcosmarxm commented Apr 11, 2024

Ellipsis 🚀 This PR description was created by Ellipsis for commit 033d82a.

Summary:

This PR modifies the .github/workflows/stale-community-issues.yaml file to rename the workflow and adjust the cron schedule.

Key points:

  • Renamed workflow in .github/workflows/stale-community-issues.yaml.
  • Adjusted cron schedule to run at exactly 9:00.

Generated with ❤️ by ellipsis.dev

@marcosmarxm marcosmarxm requested a review from a team April 11, 2024 12:23
Copy link

vercel bot commented Apr 11, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
airbyte-docs ⬜️ Ignored (Inspect) Visit Preview Apr 11, 2024 0:36am

Copy link

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Looks good to me!

  • Reviewed the entire pull request up to 033d82a
  • Looked at 15 lines of code in 1 files
  • Took 47 seconds to review
More info
  • Skipped 0 files when reviewing.
  • Skipped posting 1 additional comments because they didn't meet confidence threshold of 50%.
1. .github/workflows/stale-community-issues.yaml:4:
  • Assessed confidence : 0%
  • Comment:
    The change in the cron schedule is correct. It will now trigger the action at exactly the 9th hour (9:00) of every day, which is likely the intended behavior.
  • Reasoning:
    The change in the cron schedule from '* 9 * * *' to '0 9 * * *' is correct. The previous schedule would have triggered the action every minute of the 9th hour of every day. The new schedule will trigger the action at exactly the 9th hour (9:00) of every day, which is likely the intended behavior. No issues found in this PR.

Workflow ID: wflow_8qxs9XW0IR6dw0pt


Not what you expected? You can customize the content of the reviews using rules. Learn more here.

Copy link
Contributor

@rwask rwask left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@marcosmarxm marcosmarxm merged commit 865c106 into master Apr 11, 2024
27 checks passed
@marcosmarxm marcosmarxm deleted the marcos/update-stale-schedule branch April 11, 2024 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants