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

gh-actions: Change linting workflow schedule from daily to weekly. #69

Merged
merged 2 commits into from
Aug 7, 2024

Conversation

LinZhihao-723
Copy link
Member

References

Description

The current scheduled linting workflow runs too frequently and it frequently fails due to intensive workloads in GitHub. This failure could even propagate to the forked repos, which will bring confusion to the developers. As a solution, we decide to switch to weekly execution. Tuesday is chosen to avoid potential high GitHub traffic on Monday or Sunday.
Reference: https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#schedule

Validation performed

Ensure the current workflow passes.

kirkrodrigues
kirkrodrigues previously approved these changes Aug 7, 2024
Copy link
Member

@kirkrodrigues kirkrodrigues left a comment

Choose a reason for hiding this comment

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

Minor suggestion.

For the PR title, how about:

gh-actions: Change linting workflow schedule from daily to weekly.

.github/workflows/build_wheels.yml Outdated Show resolved Hide resolved
@LinZhihao-723 LinZhihao-723 changed the title gh-actions: Change the scheduled linting workflow from daily execution to weekly execution. gh-actions: Change linting workflow schedule from daily to weekly. Aug 7, 2024
Co-authored-by: kirkrodrigues <[email protected]>
@LinZhihao-723 LinZhihao-723 merged commit 251c880 into y-scope:main Aug 7, 2024
59 checks passed
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