Skip to content

minor monitor-components improvements #3983

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

Merged
merged 2 commits into from
Oct 31, 2022

Conversation

rimrul
Copy link
Member

@rimrul rimrul commented Aug 13, 2022

No description provided.

@rimrul rimrul marked this pull request as draft August 14, 2022 18:06
@dscho
Copy link
Member

dscho commented Oct 28, 2022

@rimrul what's the status on this? Do you need me to assist?

As we've discovered with Git 2.37.1, our workflow to inform us about component
updates can miss embargoed git releases, since GitHub usues the tag creation
date as the publication date for their feeds. To prevent similar issues with
other components in the future, let's increase the time span we look at for
new feed items, as discussed in
git-for-windows#3948 (comment)

Signed-off-by: Matthias Aßhauer <mha1993@live.de>
@rimrul rimrul force-pushed the monitor-components-improvements branch 2 times, most recently from fc53bad to 53251c8 Compare October 29, 2022 13:40
The `environment` keyword makes GitHub Actions believe this is a deployment
environment [1], but we aren't deploying anything in this workflow. Having
a "deployment" workflow on a frequent schedule causes some pull requests like
[2] to become filled with thousands of "dscho deployed temporarily to
monitor-components" messages. This was originally intended to allow this
workflow to open issues, but we can instead just specify that the workflow
should run with permissions to create issues and then use the generated
access token.

[1] https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment
[2] git-for-windows#3948

Signed-off-by: Matthias Aßhauer <mha1993@live.de>
@rimrul rimrul force-pushed the monitor-components-improvements branch from 53251c8 to c8dc900 Compare October 29, 2022 13:41
@rimrul rimrul marked this pull request as ready for review October 29, 2022 13:46
@rimrul
Copy link
Member Author

rimrul commented Oct 29, 2022

Should be good now.

Copy link
Member

@dscho dscho left a comment

Choose a reason for hiding this comment

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

Yay! Thank you @rimrul

@dscho
Copy link
Member

dscho commented Oct 31, 2022

Procedural note: since we need to rebuild cURL (after the dependency nghttp2 was built with a different DLL file name), I want to wait for https://dev.azure.com/git-for-windows/git/_build/results?buildId=108304&view=logs&j=275f1d19-1bd8-5591-b06b-07d489ea915a to finish, then kick off the two sync workflows to update git-sdk-64/git-sdk-32, and then merge this PR so that the next snapshot will be built correctly. Just in case anybody was wondering why I do not merge this PR immediately.

@dscho dscho merged commit beeaffb into git-for-windows:main Oct 31, 2022
@dscho dscho added this to the Next release milestone Oct 31, 2022
@rimrul rimrul deleted the monitor-components-improvements branch October 31, 2022 12:06
Zeze1184 added a commit to https-github-com-Zeze1184/git that referenced this pull request Nov 22, 2022
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