All workflows

Showing runs from all workflows

74 workflow runs

Push check: Update the banner to the design team's version
cancelled:
Live check#17:Commitcac8650pushedbyanil-bd
main
Sep 23, 20263s
Daily check: is anything broken?
completed successfully:
Live check#16:Scheduled
main
Sep 23, 20261m 38s
Daily check: is anything broken?
failed:
Live check#15:Scheduled
main
Sep 22, 202656s
Weekly check: does every README block still work?
completed successfully:
Live check#14:Scheduled
main
Sep 21, 20262m 39s
Stagger the scheduled runs so the scraper repos never overlap
completed successfully:
Tests (automatic, no API calls, free)#7:Commitab35362pushedbyanil-bd
main
Sep 21, 202623s
Push check: Stagger the scheduled runs so the scraper repos never overlap Every scraper repo ran its daily and Monday checks at 06:00 UTC. On Monday that is the full README matrix in all four at once, up to about sixteen jobs against one account, which is the burst that returned "Your system is sending too many of this type of request" during the LinkedIn Python build. Valid inputs fail with that error, so the runs would go red with nothing wrong in the code. The Monday runs now start at 06:00, 06:20, ...
completed successfully:
Live check#13:Commitab35362pushedbyanil-bd
main
Sep 21, 202640s
Describe this workflow, not the Instagram one it was ported from
completed successfully:
Tests (automatic, no API calls, free)#6:Commit0bb2403pushedbyanil-bd
main
Sep 20, 202624s
Push check: Describe this workflow, not the Instagram one it was ported from The header block and the scrape job's name still said "one post from nasa" and "Fetch the posts", inherited from the Instagram twin. Both are the first thing a maintainer reads, and in this repository they named the wrong thing entirely. No behaviour changes.
completed successfully:
Live check#12:Commit0bb2403pushedbyanil-bd
main
Sep 20, 202651s
Add the LinkedIn banner
completed successfully:
Tests (automatic, no API calls, free)#5:Commitf3d78b9pushedbyanil-bd
main
Sep 20, 202625s
Push check: Add the LinkedIn banner 2400x520, the LinkedIn twin of the Instagram one. The endpoint row and the subtitle are claims, and both hold: /profiles, /companies, /jobs and /posts are all in the endpoint table, collect takes URLs, and discover takes a name or a keyword. The README line was parked in a comment so the repository front page would not show a broken image before the file existed. Restored now.
completed successfully:
Live check#11:Commitf3d78b9pushedbyanil-bd
main
Sep 20, 20261m 1s
Daily check: is anything broken?
completed successfully:
Live check#10:Scheduled
main
Sep 20, 20261m 18s
Daily check: is anything broken?
completed successfully:
Live check#9:Scheduled
main
Sep 19, 20261m 14s
Badge job: start from the tip of main, so a re-run cannot conflict
completed successfully:
Tests (automatic, no API calls, free)#4:Commitb35c7afpushedbyanil-bd
main
Sep 18, 202623s
Push check: Badge job: start from the tip of main, so a re-run cannot conflict The daily run on 2026-09-18 failed with a merge conflict in README.md. Attempt 1 of that run failed its scrape job, so the badge job wrote "last check failed" and pushed it. Attempt 2, a re-run three hours later, passed and wrote "last verified". But a re-run checks out the commit the run first started on, not the current tip. So attempt 2 edited the badge line from a base that did not have attempt 1's edit to the same line,...
completed successfully:
Live check#8:Commitb35c7afpushedbyanil-bd
main
Sep 18, 202644s
Daily check: is anything broken?
failed:
Live check#7:Scheduled
main
Sep 18, 20261m 6s
Daily check: is anything broken?
completed successfully:
Live check#6:Scheduled
main
Sep 17, 20261m 32s
Scrape satyanadella
completed successfully:
Live check#5:Manually runbyanil-bd
main
Sep 17, 20261m 1s
Push check: Name the CLI pipeline that exists, and keep the pii flag in the field table Two fixes the live run surfaced. The coding-agents block called bdata pipelines linkedin_profiles, which is not a pipeline. I wrote it by analogy with instagram_posts instead of running bdata pipelines list. The real name is linkedin_person_profile. The README now names the five LinkedIn pipelines the CLI actually has. The daily field-table generator rewrote the table and dropped two things it should have kept:...
completed successfully:
Live check#4:Commit917fd35pushedbyanil-bd
main
Sep 17, 202640s
Name the CLI pipeline that exists, and keep the pii flag in the field…
completed successfully:
Tests (automatic, no API calls, free)#3:Commit917fd35pushedbyanil-bd
main
Sep 17, 202620s
Scrape satyanadella
failed:
Live check#3:Manually runbyanil-bd
main
Sep 17, 20263m 4s
Push check: Point the compliance line at a URL that exists The live check's link step caught it: brightdata.com/legal/compliance is a 404. I wrote that path from assumption instead of verifying it. The LinkedIn product page links compliance to brightdata.com/legal-governance, which returns 200. Use that. This is what the link step is for. It ran before any credit was spent, because it sits ahead of the fetch step in the same job.
failed:
Live check#2:Commite128327pushedbyanil-bd
main
Sep 17, 202632s
Point the compliance line at a URL that exists
completed successfully:
Tests (automatic, no API calls, free)#2:Commite128327pushedbyanil-bd
main
Sep 17, 202622s
The JavaScript LinkedIn twin of instagram-scraper-node
completed successfully:
Tests (automatic, no API calls, free)#1:Commit23902e1pushedbyanil-bd
main
Sep 17, 202620s
Push check: The JavaScript LinkedIn twin of instagram-scraper-node LinkedIn profiles, companies, jobs and posts as JSON, on the Bright Data LinkedIn Scraper API, through @brightdata/sdk 1.2.0. Every README code block was run against the live API and shows its real output. The sample file comes from a real run of the CLI. Examples use public figures and company pages, never a private individual. Shape differences from the Instagram twin, all documented in the README: - Every profile asked for goes in ...
failed:
Live check#1:Commit23902e1pushedbyanil-bd
main
Sep 17, 202643s