Automatically publish posts from GTN #2068
Merged
Conversation
This file contains 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
GitHub Actions workflow that automatically creates PRs to publish Galaxy Training Network news as external links.
Co-authored-by: Björn Grüning <[email protected]>
Resorts to an approach purely based on the GitHub API.
kysrpex
added
new-feature
dannon
approved these changes
Jul 6, 2023
|
Thank you, @kysrpex! |
|
this is not the direction I expected when I said the last yaml was too complicated 😅 but glad you've got something working! l |
Sign up for free
to 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.
GitHub Actions workflow that automatically creates PRs to publish Galaxy Training Network news as external links.
Closes #1417. Folow-up of #2065.
An example PR created by this workflow is available here. An example workflow run is available here.
This PR hopefully addresses all the feedback from #2065, namely:
In addition, the whole approach has been reworked. The workflow uses now just feedparser and the GitHub REST API (through GitHub CLI and curl). Hopefully it is significantly faster (I cannot compare since I deleted the repo) as it avoids checking out the code.