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

chore: make the update-contributors workflow run monthly #3632

Merged
merged 2 commits into from
Oct 17, 2024

Conversation

aleks-p
Copy link
Contributor

@aleks-p aleks-p commented Oct 16, 2024

Fixes #3574 by scheduling the workflow to run on the first day Sunday of every month and removing the [skip ci] flag in the commit.

We don't really need frequent updates imo and if we run it monthly we don't have to worry about it being wasteful.

There is a small chance of jobs getting cancelled if someone merges a PR right around when this runs (midnight UTC, on the first day of the month), I don't think this is a real problem but we could update the concurrency config if it becomes an issue.
This probability is now reduced by having it run on the first Sunday of the month, at 00:00 UTC.

@aleks-p aleks-p requested a review from a team as a code owner October 16, 2024 11:54
Copy link
Contributor

@marcsanmi marcsanmi left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@@ -24,7 +24,7 @@ jobs:
git config --local user.email '[email protected]'
if ! git diff --exit-code README.md; then
git add README.md
git commit -m 'docs: updates the list of contributors in README [skip ci]'
Copy link
Contributor

Choose a reason for hiding this comment

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

Another option would be to run it monthly but keep the skip ci flag to avoid having an image tied to this commit. The only necessary check would be to schedule it for Wednesday(?), to allow some buffer after our release day.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I am unsure about bringing back the skip ci flag. If we have a slow week (not many PRs merged), we can get in the same situation again where we can't cut a release. If there are no PRs merged between that Wednesday and Monday, the weekly release will fail and if we decide to make the official release on the same Wednesday it can break too.

@marcsanmi marcsanmi requested a review from a team October 16, 2024 20:11
@aleks-p aleks-p merged commit b53c2b5 into main Oct 17, 2024
18 checks passed
@aleks-p aleks-p deleted the chore/schedule-contributor-update branch October 17, 2024 13:43
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.

Improve update contributors CI
3 participants