Skip to content

feat(linkedin): consolidate profile, jobs, posts, and projects readers#1731

Merged
jackwener merged 10 commits into
mainfrom
consolidate/linkedin-readers
May 23, 2026
Merged

feat(linkedin): consolidate profile, jobs, posts, and projects readers#1731
jackwener merged 10 commits into
mainfrom
consolidate/linkedin-readers

Conversation

@jackwener
Copy link
Copy Markdown
Owner

Consolidates LinkedIn PRs #1722, #1723, #1724, #1725, #1726, and #1727 into one reviewable carrier.

Included changes:

  • profile-read, profile-analytics, services-read
  • jobs-preferences and job-detail
  • posts and post-analytics
  • timeline text normalization
  • profile-projects
  • docs/README/index updates and regenerated manifest

Local validation:

  • npm ci
  • npm run typecheck
  • npx vitest run --project adapter clis/linkedin/*.test.js
  • npm run build
  • npm run docs:build
  • node --check touched LinkedIn files + dist/src/main.js
  • npm run check:typed-error-lint
  • npm run check:silent-column-drop
  • npm run advise:listing-id-pairing
  • git diff --check

@gauravsaxena1997
Copy link
Copy Markdown
Contributor

Hi @jackwener , thanks for consolidating and merging the LinkedIn readers work.

I noticed that PR #1731 was squash-merged as a single commit authored by jackwener, while the six original commits from PRs #1722-#1727 were authored by gauravsaxena1997.

Because those original commits are not reachable from main, GitHub’s contributors graph/API does not credit them to my account. Would you be open to preserving my authorship for those commits?

Possible options:

  • replace the squash commit with the original commits authored by me, if rewriting history is acceptable
  • revert the squash commit and re-merge/cherry-pick the original commits preserving author metadata
  • for future PRs, use merge/rebase instead of squash when preserving contributor attribution matters

No worries if rewriting history is not practical, but I wanted to ask since this affects GitHub contributor attribution.

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