chore: Update node popularity data#792
Open
github-actions[bot] wants to merge 1 commit intomasterfrom
Open
Conversation
github-actions
bot
force-pushed
the
update-node-popularity
branch
2 times, most recently
from
9fa500b to
4e5a6e0
Compare
github-actions
bot
force-pushed
the
update-node-popularity
branch
from
4e5a6e0 to
2846651
Compare
github-actions
bot
force-pushed
the
update-node-popularity
branch
from
2846651 to
12ccae1
Compare
github-actions
bot
force-pushed
the
update-node-popularity
branch
from
12ccae1 to
90fd78c
Compare
github-actions
bot
force-pushed
the
update-node-popularity
branch
2 times, most recently
from
b354770 to
e5949ba
Compare
github-actions
bot
force-pushed
the
update-node-popularity
branch
from
e5949ba to
af0d30a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This automated PR updates the node popularity data used for sorting nodes in the node creator panel.
The data is fetched weekly from the n8n telemetry endpoint to reflect current usage patterns.
Generated by the weekly node popularity update workflow.