Skip to content

Conversation

@fnune
Copy link
Member

@fnune fnune commented Nov 13, 2025

Renamed workflows for clarity:

  • generate-package-metadata.yml to poll-community-packages.yml
  • publish-provider-update.yml to on-provider-update.yml

Updated display names and added documentation comments explaining provider types, duplicate checking strategy, and event handling.

Renamed workflows for clarity:
- generate-package-metadata.yml to poll-community-packages.yml
- publish-provider-update.yml to on-provider-update.yml

Updated display names and added documentation comments explaining
provider types, duplicate checking strategy, and event handling.
@github-actions
Copy link

Your site preview for commit 0dbeb53 is ready! 🎉

http://registry--origin-pr-9156-0dbeb534.s3-website.us-west-2.amazonaws.com/registry.

Copy link
Contributor

@danielrbradley danielrbradley left a comment

Choose a reason for hiding this comment

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

This looks like an improvement to me .. not to bike-shed around this but if we want to keep iterating ...

Perhaps we should keep the name and filename in-line .. perhaps name "Handle Provider Update Events" handle-provider-update-events.yml?

I'm trying to think if there's any risk around some other systems depending on these names, but I think we should be safe as they're not reusable workflows.

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