Uh oh!
There was an error while loading. Please reload this page.
feat: publish releases to LinkedIn - #194
Merged
Merged
Conversation
Adds optional telegram-chat-id/telegram-bot-token to the shared workflow so consumers get a Telegram message on success or failure without wiring a separate notification workflow. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
There was a problem hiding this comment.
🟡 Changes recommended
There are confirmed edge cases where truncation helpers can exceed the requested limit and the optional Telegram notify job can run without a provided bot token, leading to avoidable runtime failures.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Adds a first-party Baseline integration to publish stable GitHub Releases to a maintainer’s LinkedIn member feed via a reusable workflow, keeping the post content deterministic (repository + release metadata) and exposing the resulting LinkedIn post URN.
Changes:
- Introduces reusable workflow(s) to publish release posts to LinkedIn (with optional Telegram notifications) and a local Baseline caller workflow.
- Adds two composite actions: one to format release content into LinkedIn “little” text, and one to resolve the member URN + publish via the LinkedIn REST API.
- Adds README documentation and a focused Python test suite covering formatting, API behavior, and workflow wiring.
File summaries
| File | Description |
|---|---|
test/test_linkedin_release.py | Adds unit tests for message formatting, LinkedIn API request/response handling, and workflow/action wiring. |
README.md | Documents consumer setup for the LinkedIn release publishing workflow, token rotation expectations, and retry guidance. |
.github/workflows/publish-linkedin-release.yml | Adds Baseline’s local caller workflow triggered on release.published. |
.github/workflows/publish-linkedin-release-shared.yml | Adds the reusable workflow implementing LinkedIn publishing + optional Telegram notifications. |
.github/actions/send-linkedin-post/send.py | Implements LinkedIn userinfo lookup and post publishing via urllib. |
.github/actions/send-linkedin-post/action.yml | Composite action wrapper for the LinkedIn sender script. |
.github/actions/prepare-linkedin-release-post/prepare.py | Implements deterministic conversion of release content to LinkedIn little text, including escaping/truncation/hashtags. |
.github/actions/prepare-linkedin-release-post/action.yml | Composite action wrapper for the LinkedIn formatter script. |
Review details
Suppressed comments (1)
.github/actions/prepare-linkedin-release-post/prepare.py:29
truncate_little_text()can also exceedlimitwhenlimit <= 3(it returns...unconditionally), which can violateLINKEDIN_POST_LIMITifdescription_limitis computed as 1–3 chars. Add a small-limit guard before calculatingavailable = limit - 3.
escaped = escape_little_text(value)
if len(escaped) <= limit:
return escaped
available = limit - 3
- Files reviewed: 8/8 changed files
- Comments generated: 2
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+14
to
+17
| def truncate(value, limit): | ||
| if len(value) <= limit: | ||
| return value | ||
| return value[: limit - 3].rstrip() + "..." |
Comment on lines
+44
to
+47
| if: >- | ||
| always() && | ||
| inputs.telegram-chat-id != '' && | ||
| (needs.publish.result == 'success' || needs.publish.result == 'failure') |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Testing
python3 -m unittest discover -s test -v(83 tests)pre-commit run --files README.md .github/actions/prepare-linkedin-release-post/action.yml .github/actions/prepare-linkedin-release-post/prepare.py .github/actions/send-linkedin-post/action.yml .github/actions/send-linkedin-post/send.py .github/workflows/publish-linkedin-release-shared.yml .github/workflows/publish-linkedin-release.yml test/test_linkedin_release.pygit diff --checkNo live LinkedIn post was created during testing.
Closes#193