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

Start monitoring updates of Git for Windows' components in the open #2837

Merged
merged 1 commit into from
Oct 7, 2020

Conversation

dscho
Copy link
Member

@dscho dscho commented Sep 29, 2020

I currently use private IFTTT Applets to get notified whenever a new version was released of a component bundled in Git for Windows.

There are two problems with that:

  • This is totally opaque to the community
  • IFTTT will stop supporting so many applets in their free plan

Let's use the power of GitHub workflows to address both issues.

@rimrul
Copy link
Member

rimrul commented Sep 29, 2020

Do we need to prepare all those labels or does it create them on it's own? And should each component really have it's own label or should we maybe just have one label like package-upgrade? The prefix should make it clear which package needs upgrading and one label might make filtering for package upgrades and addressing multiple issues in a row easier.

@dscho
Copy link
Member Author

dscho commented Sep 29, 2020

By default, there is no prefix, and the new issue's label is set to the title of the Atom feed entry. In most cases, this does not repeat the package name, hence my manual addition of the prefix.

If you want an extra label to be added, just for these new tickets, that's fine. What do you propose? new-version? component-update? update?

@rimrul
Copy link
Member

rimrul commented Sep 29, 2020

Yes, the prefix: … line is good, but I'm just not sure the labels: … line is great. Unless I'm missunderstanding how this works that line tries to add the package name as a github label (in addition to the prefix that conveys the same info).

@dscho
Copy link
Member Author

dscho commented Sep 29, 2020

Unless I'm missunderstanding how this works that line tries to add the package name as a github label (in addition to the prefix that conveys the same info).

No, your understanding is right. Would you rather have a generic label that applies to all of these tickets? If so, which one?

@@ -0,0 +1,68 @@
name: Monitor component updates

This comment was marked as spam.

@dscho
Copy link
Member Author

dscho commented Oct 2, 2020

@rimrul I changed it so that the component-update label is used, and the prefix is now a bit more informative. Sound good?

@rimrul
Copy link
Member

rimrul commented Oct 2, 2020

LGTM

Rather than using private IFTTT Applets that send mails to this
maintainer whenever a new version of a Git for Windows component was
released, let's use the power of GitHub workflows to make this process
publicly visible.

This workflow monitors the Atom/RSS feeds, and opens a ticket whenever a
new version was released.

Signed-off-by: Johannes Schindelin <[email protected]>
@dscho dscho merged commit 0b6a63d into git-for-windows:main Oct 7, 2020
@dscho dscho deleted the monitor-component-updates branch October 7, 2020 14:13
git-for-windows-ci pushed a commit that referenced this pull request Oct 7, 2020
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 7, 2020
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 7, 2020
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 7, 2020
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 7, 2020
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 8, 2020
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 8, 2020
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 8, 2020
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 8, 2020
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 8, 2020
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 8, 2020
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 9, 2020
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 9, 2020
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 9, 2020
Start monitoring updates of Git for Windows' component in the open
dscho added a commit to dscho/git that referenced this pull request Oct 9, 2020
…updates

Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 9, 2020
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 9, 2020
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 9, 2020
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 9, 2024
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 9, 2024
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 9, 2024
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 9, 2024
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 9, 2024
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 10, 2024
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 10, 2024
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 10, 2024
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 10, 2024
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 10, 2024
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 11, 2024
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 11, 2024
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 11, 2024
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 11, 2024
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 11, 2024
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 20, 2024
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 20, 2024
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 21, 2024
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 21, 2024
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 21, 2024
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 22, 2024
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 22, 2024
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 22, 2024
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 22, 2024
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 22, 2024
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 22, 2024
Start monitoring updates of Git for Windows' component in the open
dscho added a commit that referenced this pull request Oct 23, 2024
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 25, 2024
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 25, 2024
Start monitoring updates of Git for Windows' component in the open
git-for-windows-ci pushed a commit that referenced this pull request Oct 25, 2024
Start monitoring updates of Git for Windows' component in the open
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.

3 participants