All workflows

Workflow runs

• Push check: Trim the contributing guide

  completed successfully:
  Live check#15:Commit437af5epushedbyanil-bd
  main

  Sep 24, 20261m 22s
  More actions for workflow run 15

• Trim the contributing guide

  completed successfully:
  Tests (automatic, no API calls, free)#8:Commit437af5epushedbyanil-bd
  main

  Sep 24, 202631s
  More actions for workflow run 8

• Add a short contributing guide

  completed successfully:
  Tests (automatic, no API calls, free)#7:Commit3146300pushedbyanil-bd
  main

  Sep 24, 202627s
  More actions for workflow run 7

• Push check: Add a short contributing guide

  completed successfully:
  Live check#14:Commit3146300pushedbyanil-bd
  main

  Sep 24, 20261m 0s
  More actions for workflow run 14

• Drop the note about the repository being private

  completed successfully:
  Tests (automatic, no API calls, free)#6:Commite137035pushedbyanil-bd
  main

  Sep 23, 202623s
  More actions for workflow run 6

• Push check: Drop the note about the repository being private

  completed successfully:
  Live check#13:Commite137035pushedbyanil-bd
  main

  Sep 23, 202657s
  More actions for workflow run 13

• Update the banner to the design team's version

  completed successfully:
  Tests (automatic, no API calls, free)#5:Commit5678f8bpushedbyanil-bd
  main

  Sep 23, 202623s
  More actions for workflow run 5

• Push check: Update the banner to the design team's version

  completed successfully:
  Live check#12:Commit5678f8bpushedbyanil-bd
  main

  Sep 23, 202652s
  More actions for workflow run 12

• Daily check: is anything broken?

  completed successfully:
  Live check#11:Scheduled
  main

  Sep 23, 20262m 0s
  More actions for workflow run 11

• Daily check: is anything broken?

  completed successfully:
  Live check#10:Scheduled
  main

  Sep 22, 20261m 56s
  More actions for workflow run 10

• Weekly check: does every README block still work?

  completed successfully:
  Live check#9:Scheduled
  main

  Sep 21, 20262m 15s
  More actions for workflow run 9

• 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#8:Commit38a7dc8pushedbyanil-bd
  main

  Sep 21, 202658s
  More actions for workflow run 8

• Stagger the scheduled runs so the scraper repos never overlap

  completed successfully:
  Tests (automatic, no API calls, free)#4:Commit38a7dc8pushedbyanil-bd
  main

  Sep 21, 202654s
  More actions for workflow run 4

• 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#7:Commit5bdf05dpushedbyanil-bd
  main

  Sep 20, 202648s
  More actions for workflow run 7

• Add the LinkedIn banner

  completed successfully:
  Tests (automatic, no API calls, free)#3:Commit5bdf05dpushedbyanil-bd
  main

  Sep 20, 202623s
  More actions for workflow run 3

• Daily check: is anything broken?

  completed successfully:
  Live check#6:Scheduled
  main

  Sep 20, 20261m 19s
  More actions for workflow run 6

• Daily check: is anything broken?

  completed successfully:
  Live check#5:Scheduled
  main

  Sep 19, 20261m 36s
  More actions for workflow run 5

• Scrape satyanadella

  completed successfully:
  Live check#4:Manually runbyanil-bd
  main

  Sep 18, 20261m 11s
  More actions for workflow run 4

• Live check: a failed block shows why, not only its last line

  completed successfully:
  Tests (automatic, no API calls, free)#2:Commitc43bc69pushedbyanil-bd
  main

  Sep 18, 202655s
  More actions for workflow run 2

• Push check: Live check: a failed block shows why, not only its last line The README's CLI block failed with "Saved 1 of 2 profiles", which is the one line that says nothing about the cause. The line naming the profile that failed, and its error, sat just above it and was discarded, so the run could not be diagnosed from its own log. A failing block now shows its failure lines: the CLI's "failed slug: ..." lines, or any line carrying an Error. It falls back to the last six lines.

  completed successfully:
  Live check#3:Commitc43bc69pushedbyanil-bd
  main

  Sep 18, 20261m 40s
  More actions for workflow run 3

• Scrape satyanadella

  failed:
  Live check#2:Manually runbyanil-bd
  main

  Sep 18, 20262m 24s
  More actions for workflow run 2

• Push check: The Python LinkedIn twin of linkedin-scraper-node LinkedIn profiles, companies, jobs and posts as JSON, on the Bright Data LinkedIn Scraper API, through brightdata-sdk 2.5.2. Every README code block was extracted from the README itself and run against the live API, and shows its real output. The sample file comes from a real run of the CLI. The SDK mislabels list results. With several URLs it pairs rows with inputs by position, and the API returns rows in a different order each run. Measur...

  failed:
  Live check#1:Commit18eab5cpushedbyanil-bd
  main

  Sep 18, 202639s
  More actions for workflow run 1

• The Python LinkedIn twin of linkedin-scraper-node

  completed successfully:
  Tests (automatic, no API calls, free)#1:Commit18eab5cpushedbyanil-bd
  main

  Sep 18, 202628s
  More actions for workflow run 1