Skip to content

chore: sync generated content from apify-plugins - #22

Open
apify-service-account wants to merge 1 commit into
mainfrom
apify-plugins-sync/2485a1d9
Open

chore: sync generated content from apify-plugins#22
apify-service-account wants to merge 1 commit into
mainfrom
apify-plugins-sync/2485a1d9

Conversation

@apify-service-account

Copy link
Copy Markdown

Automated PR opened by the apify-plugins CI pipeline.

Source commit: apify/apify-plugins-internal@2485a1d9
Trigger: push to main
Workflow run: #33

This PR updates generated content (skills, rules, MCP config, manifests) with the latest build output. Files not produced by the build are left untouched.

⚠️ Overlay sync — files removed from the source build are not deleted here. If a generated file was renamed or removed upstream, please delete the orphaned copy manually before merging.

Please review the diff before merging.

@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown

૮ >ﻌ< ა ci review

ran on ce58f5b — chore: sync generated content from apify-plugins (2485a1d9)

❌ Job failures

Check contributors / check-attribution · View job

Job Check contributors / check-attribution failed.


⚠️ Action required

Unmapped contributor email(s) · View job

New contributor email(s) are not in AUTHOR_MAP.

apify-plugins-bot@users.noreply.github.com (apify-plugins-bot)

How to fix:

Run from the PR branch:

python3 scripts/audit_pr_attribution.py --fix
git add contributors && git commit -m "chore: map contributor emails" && git push

Or map one email manually (do NOT edit AUTHOR_MAP in release.py):

python3 scripts/add_contributor.py <email> <github-username>

To find the GitHub username for an email:

gh api 'search/users?q=EMAIL+in:email' --jq '.items[0].login'

debug info

CI timings

CI timings · View report · View job

Wall time 1440m21s (no baseline yet).

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.

1 participant