Closed d33bs closed 1 year ago
Name | Link |
---|---|
Latest commit | 76a853f15559928afacdbd80936c9e7c7d0cb51b |
Latest deploy log | https://app.netlify.com/sites/set-website/deploys/64186c95f08bff000722f251 |
Deploy Preview | https://deploy-preview-16--set-website.netlify.app/2023/03/15/automate-software-workflows-with-github-actions |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
Idea for rewording:
For example, one can use Github Actions to make sure code in a Github Pull Request passes certain tests before it is allowed to be merged.
{% include figure.html image="images/github_actions_tab.png" caption="Image showing Github Actions tab on Github website." %} {:.center}
For some reason the markdown parser is applying this to the following paragraph. The center shouldn't be needed for the figure component.
Ideas for rewording:
GitHub provides an βActionsβ tab for each repository which helps visualize and control Github Actions workflow runs. This tab shows a history of all workflow runs in the repository. For each run, it shows whether it was run successful or not, the associated logs, and controls to cancel or re-run it.
Maybe it's worth mentioning reusable workflows from within GitHub Actions itself, for "nested workflows". Or maybe I'm misunderstanding what nested workflows really means (I've never used Dagger).
Maybe some brief conclusion, perhaps mentioning the overall benefits of productivity, thoroughness, error-proofing, etc.
Thank you @vincerubinetti and @falquaddoomi ! I took time to address your comments and will go ahead with merging.
This PR adds a new tip of the week blog post titled "Automate Software Workflows with GitHub Actions". The focus here was on providing a baseline understanding and inspiration for software workflow engines, Github Actions, and environments reproducibility (with context to software workflows). As part of this post, supplemental demonstration content was created via CU-DBMI/demo-github-actions#1 to help show how features look in real-life and reduce the barriers to entry for learning about this feature from Github alongside third-party tools.
Thank you in advance for your thoughts, comments, and suggestions!