Publish GitHub releases to LinkedIn automatically

[ineedjet]

Goal

Increase the maintainer profile discoverability on LinkedIn by automatically turning releases of public projects into posts. The posts should expose the technologies used by the repository, provide varied evidence of ongoing engineering work, and invite readers to star the project without requiring routine manual management.

Post content

Build each post from repository-owned sources:

• a dedicated README section containing the canonical product description;
• the GitHub Release name, body, and URL;
• the repository URL and a short request to star the project;
• all repository Topics, used verbatim and prefixed with #.

Example shape:

{repository} {release_name}

{canonical_product_description}

{release_body}

{release_url}

If you find the project useful, consider giving it a star on GitHub:
{repository_url}

#{topic-1} #{topic-2} #{topic-3}

Publication behavior

Publish to the maintainer personal LinkedIn feed when a stable GitHub Release is published. Skip drafts and prereleases, avoid duplicate posts on workflow retries, and retain the resulting LinkedIn post identifier for diagnostics.

Keep the implementation inexpensive and deterministic: use the existing release text directly rather than introducing LLM generation. The automation should be reusable across public repositories, with LinkedIn credentials supplied through GitHub Actions secrets. Account for LinkedIn access-token expiration and API version sunset as operational constraints.