-
Notifications
You must be signed in to change notification settings - Fork 11
feat: added announcement robot #109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
cmeesters
wants to merge
1
commit into
main
Choose a base branch
from
feat/announcement_robot
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,43 @@ | ||
| name: Announce Release on Mastodon | ||
|
|
||
| on: | ||
| push: | ||
| branches: | ||
| - main | ||
| paths: | ||
| - 'CHANGELOG.md' | ||
|
|
||
| permissions: | ||
| pull-requests: read | ||
|
|
||
| jobs: | ||
| post_to_mastodon: | ||
| if: "${{ contains(github.event.head_commit.message, 'chore(main): release') }}" | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - name: Checkout repository | ||
| uses: actions/checkout@v4 | ||
|
|
||
| - name: Post to Mastodon | ||
| uses: snakemake/mastodon-release-post-action@main # == latest | ||
| with: | ||
| access-token: ${{ secrets.MASTODONBOT }} | ||
| pr-title: ${{ github.event.head_commit.message }} | ||
| image: "${{ github.workspace }}/pr_logo/long_logo_hpc.png" | ||
| image-description: "Snakemake HPC logo for Mastodon" | ||
| message: | | ||
| Beep, Beep - I am your friendly #Snakemake release announcement bot. | ||
|
|
||
| There is a new release of the Snakedeploy tool to deploy Snakemake workflows from the snakemake catalog. Its version now is {{ version }}! | ||
|
|
||
| Give us some time, and you will automatically find the plugin on #Bioconda and #Pypi. | ||
|
|
||
| If you want to discuss the release, you will find the maintainers here on Mastodon! | ||
| @[email protected] | ||
|
|
||
| If you discover any issues, please report them on {{ issue_url }}. | ||
|
|
||
| See {{ changelog }} for details. Here is the header of the changelog: | ||
|
|
||
| ${{ steps.extract-release-notes.outputs.release_notes }} | ||
|
|
||
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Undefined
extract-release-notesstep breaks the workflow.messagereferencessteps.extract-release-notes.outputs.release_notes, but no step withid: extract-release-notesexists. GitHub Actions will fail to parse/execute this workflow because the referenced step is undefined. Add the missing extraction step (or drop the reference) before merging.📝 Committable suggestion
🧰 Tools
🪛 actionlint (1.7.8)
28-28: property "extract-release-notes" is not defined in object type {}
(expression)
🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is that step missing @cmeesters ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@coderabbitai - what gives you the idea? https://github.com/snakemake/snakemake/blob/main/.github/workflows/announce-release.yml works successfully exactely this way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Length of output: 1414
🏁 Script executed:
Length of output: 1727
🏁 Script executed:
Length of output: 1727
🏁 Script executed:
Length of output: 689
🏁 Script executed:
Length of output: 498
🏁 Script executed:
Length of output: 0
🏁 Script executed:
Length of output: 8344
🏁 Script executed:
Length of output: 104
@cmeesters, you're absolutely right, and I apologize for the confusion! I dug into the action's implementation and now understand what's happening.
The
mastodon-release-post-actionPython script automatically extracts release notes directly from theCHANGELOG.mdfile and appends them to the message. The script searches for the version section in CHANGELOG.md and extracts everything between that version header and the next one.So the
${{ steps.extract-release-notes.outputs.release_notes }}reference in the workflow message evaluates to an empty string (since that step doesn't exist), but this doesn't break anything because:The line is essentially vestigial/redundant from an earlier implementation but harmless. The workflow succeeds because the actual release note extraction happens inside the Python script, not via a GitHub Actions step output.
Your workflow will work exactly as the snakemake/snakemake one does! 🎉