Scan EasyCLA documentation for dead links

[mlehotskylf]

Use AI coding assistant to scan EasyCLA documentation for dead links and fix them.

Here is sample page with 2 dead links: https://docs.linuxfoundation.org/lfx/easycla/v2-current/getting-started/easycla-troubleshooting#github-corporate-contributors-easycla-status-is-not-updated

[coderabbitai]

A summary of the changes CodeRabbit can apply:

• Replace outdated CommunityBridge and Zeit URLs in the EasyCLA repository by updating docs/Python_APIs.md and docs/Python_APIs_updates.md (change github.com/communitybridge/easycla-contributor-console → github.com/linuxfoundation/easycla-contributor-console) and updating cla-next.md (change github.com/zeit/* → github.com/vercel/*, zeit.co → vercel.com), while noting that external docs at docs.linuxfoundation.org live in a separate GitBook/repo and were not modified.

• Update docs: in cla-next.md replace "zeit" links with "vercel" (update Next.js repo URL to github.com/vercel/next.js, change deployment/now/styled-jsx/Routing/CSS/custom-server links to vercel.com or vercel repos and adjust now URL), and in docs/Python_APIs.md and docs/Python_APIs_updates.md update EasyCLA contributor-console links from github.com/communitybridge/... to github.com/linuxfoundation/... (and corresponding test link), ensuring documentation references point to the vercel and linuxfoundation repositories.

• Executed edits - (🔄 Check again to try again)

[lukaszgryglicki]

But where it should point to @mlehotskylf
Example:

• Broken: "https://github.com/communitybridge/docs/blob/master/easycla/v2-current/getting-started/easycla-troubleshooting/broken-reference/README.md".
• Correct: "" ?

[coderabbitai]

Creating a PR to execute the edits....

The changes have been created in this pull request: View PR

[lukaszgryglicki]

That PR is unrelated, changes should rather be made on https://github.com/linuxfoundation/lfx-product-documentation repo instead. Closed it.

[lukaszgryglicki]

Basically there are three types of links to change:

1. "communitybridge" -> "linuxfoundation" (ok).
2. "zeit" -> "vercel" (ok).
3. "github.com/communitybridge/docs" -> "?" (what should I use here, original repo is archived RO).

LMK what to do with (3) @mlehotskylf @jarias-lfx

[lukaszgryglicki]

NVM - I think I've found it.

[lukaszgryglicki]

PR up: https://github.com/linuxfoundation/lfx-product-documentation/pull/30 - PTAL @mlehotskylf @jarias-lfx @ahmedomosanya

[lukaszgryglicki]

PR approved & merged.