Creating GitHub Actions for community engagement
While in the Open Source Fellows Cohort, I got the opportunity to learn and become familiar with GitHub actions. Before this opportunity, I had never tried creating an action and was only vaguely aware of them. I mostly noticed them in "action" when I saw a neat message after I committed code on GitHub 😅. Creating one wasn't as simple as I would have thought. But their benefits, specifically when collaborating with a team, make them all the more worthwhile to learn about and implement.
According to the docs, "A workflow is a configurable automated process, authored in YAML and running one or more jobs." For example, in open-source projects, which often receive new updates and contributors, the number of tasks needed can become overwhelming depending on the number of contributors working on the project. That's where workflows, such as on CI/CD pipelines, can benefit from having actions delegating and lowering the number of repetitive tasks done manually to keep the project running smoothly.