Skip to content

docs: add snakemake logo to automatic mastodon release posts#3764

Merged
johanneskoester merged 1 commit intomainfrom
fix/image_posting_mastodon
Oct 2, 2025
Merged

docs: add snakemake logo to automatic mastodon release posts#3764
johanneskoester merged 1 commit intomainfrom
fix/image_posting_mastodon

Conversation

@cmeesters
Copy link
Copy Markdown
Member

@cmeesters cmeesters commented Oct 1, 2025

The mastodon release action has accidentally not been updated. So, no logo image has been appended. This is now fixed upstream. Yet, the image path does not to be indicated as the announcement post action crawls for it (hopefully ;-) ).

Summary by CodeRabbit

  • Chores
    • Improved release announcement automation for social posts by adjusting how the logo image is referenced when publishing to Mastodon. This increases reliability so the image consistently appears in release announcements. No changes to application features or user workflows; this is an infrastructure tweak to the publishing pipeline, with all other settings and behavior remaining the same.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Oct 1, 2025

📝 Walkthrough

Walkthrough

Updated the Mastodon action’s image input in .github/workflows/announce-release.yml from a workspace-prefixed path to a relative path ("logo_dark.png"). No other fields, steps, or control flow were modified.

Changes

Cohort / File(s) Change Summary
GitHub Actions: Announce Release
.github/workflows/announce-release.yml
Switched Mastodon post action image input from "${{ github.workspace }}/images/logo_dark.png" to "logo_dark.png"; no other workflow logic changed.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5–10 minutes

Possibly related PRs

  • docs: mastodon announcements #3723 — Introduces the same workflow and sets the Mastodon image to "${{ github.workspace }}/images/logo_dark.png", which this PR modifies to a relative path.

Suggested reviewers

  • johanneskoester

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description Check ⚠️ Warning The pull request description describes the issue and fix but does not follow the repository’s required template, as it lacks the QC section with checkboxes for test coverage and documentation updates. Please update the description to match the template by adding the “### QC” section and checkboxes indicating whether a test case covers the change and whether documentation updates are needed or unnecessary.
✅ Passed checks (2 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
Title Check ✅ Passed The title clearly and succinctly describes the primary change, namely adding the Snakemake logo to automatic Mastodon release posts, and aligns directly with the workflow update in the pull request.
✨ Finishing touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/image_posting_mastodon

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f1517e8 and 44ba68b.

📒 Files selected for processing (1)
  • .github/workflows/announce-release.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (41)
  • GitHub Check: tests (10, ubuntu-latest, py311)
  • GitHub Check: tests (10, windows-2022, py313)
  • GitHub Check: tests (10, ubuntu-latest, py313)
  • GitHub Check: tests (8, ubuntu-latest, py313)
  • GitHub Check: tests (9, ubuntu-latest, py311)
  • GitHub Check: tests (9, windows-2022, py313)
  • GitHub Check: tests (10, ubuntu-latest, py312)
  • GitHub Check: tests (8, windows-2022, py313)
  • GitHub Check: tests (9, ubuntu-latest, py312)
  • GitHub Check: tests (9, ubuntu-latest, py313)
  • GitHub Check: tests (8, ubuntu-latest, py312)
  • GitHub Check: tests (7, ubuntu-latest, py311)
  • GitHub Check: tests (8, ubuntu-latest, py311)
  • GitHub Check: tests (7, ubuntu-latest, py312)
  • GitHub Check: tests (6, ubuntu-latest, py313)
  • GitHub Check: tests (7, windows-2022, py313)
  • GitHub Check: tests (5, windows-2022, py313)
  • GitHub Check: tests (6, windows-2022, py313)
  • GitHub Check: tests (5, ubuntu-latest, py312)
  • GitHub Check: tests (7, ubuntu-latest, py313)
  • GitHub Check: tests (6, ubuntu-latest, py312)
  • GitHub Check: tests (4, windows-2022, py313)
  • GitHub Check: tests (6, ubuntu-latest, py311)
  • GitHub Check: tests (5, ubuntu-latest, py313)
  • GitHub Check: tests (5, ubuntu-latest, py311)
  • GitHub Check: tests (2, windows-2022, py313)
  • GitHub Check: tests (4, ubuntu-latest, py313)
  • GitHub Check: tests (3, macos-latest, py313)
  • GitHub Check: tests (3, ubuntu-latest, py312)
  • GitHub Check: tests (4, ubuntu-latest, py311)
  • GitHub Check: tests (3, ubuntu-latest, py313)
  • GitHub Check: tests (3, windows-2022, py313)
  • GitHub Check: tests (4, ubuntu-latest, py312)
  • GitHub Check: tests (3, ubuntu-latest, py311)
  • GitHub Check: tests (1, windows-2022, py313)
  • GitHub Check: tests (2, ubuntu-latest, py313)
  • GitHub Check: tests (2, ubuntu-latest, py312)
  • GitHub Check: tests (2, ubuntu-latest, py311)
  • GitHub Check: tests (1, ubuntu-latest, py313)
  • GitHub Check: tests (1, ubuntu-latest, py312)
  • GitHub Check: tests (1, ubuntu-latest, py311)

Comment thread .github/workflows/announce-release.yml
@johanneskoester johanneskoester changed the title fix: image posting docs: add snakemake logo to automatic mastodon release posts Oct 2, 2025
@johanneskoester johanneskoester enabled auto-merge (squash) October 2, 2025 09:25
@johanneskoester johanneskoester merged commit 7b66250 into main Oct 2, 2025
109 of 114 checks passed
@johanneskoester johanneskoester deleted the fix/image_posting_mastodon branch October 2, 2025 09:29
johanneskoester pushed a commit that referenced this pull request Oct 2, 2025
🤖 I have created a release *beep* *boop*
---


##
[9.11.8](v9.11.7...v9.11.8)
(2025-10-02)


### Bug Fixes

* use proper callable when accessing rule proxy with associated path
modifier ([#3763](#3763))
([b5d12c8](b5d12c8))


### Documentation

* add snakemake logo to automatic mastodon release posts
([#3764](#3764))
([7b66250](7b66250))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
kjohnsen pushed a commit to kjohnsen/snakemake that referenced this pull request Dec 15, 2025
…ke#3764)

The mastodon release action has accidentally not been updated. So, no
logo image has been appended. This is now fixed upstream. Yet, the image
path does not to be indicated as the announcement post action crawls for
it (hopefully ;-) ).


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Chores**
* Improved release announcement automation for social posts by adjusting
how the logo image is referenced when publishing to Mastodon. This
increases reliability so the image consistently appears in release
announcements. No changes to application features or user workflows;
this is an infrastructure tweak to the publishing pipeline, with all
other settings and behavior remaining the same.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
kjohnsen pushed a commit to kjohnsen/snakemake that referenced this pull request Dec 15, 2025
🤖 I have created a release *beep* *boop*
---


##
[9.11.8](snakemake/snakemake@v9.11.7...v9.11.8)
(2025-10-02)


### Bug Fixes

* use proper callable when accessing rule proxy with associated path
modifier ([snakemake#3763](snakemake#3763))
([b5d12c8](snakemake@b5d12c8))


### Documentation

* add snakemake logo to automatic mastodon release posts
([snakemake#3764](snakemake#3764))
([7b66250](snakemake@7b66250))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
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