This GitHub Action (GHA), is designed to move issues to a specific column based on criteria such as a specific label, or specific phrase in the issue's body. This will prove helpful for members of a team who manages a GitHub project board, such as project managers, by lessening errors and organizing workflow. By design, it abstracts a lot of the configuration into one file, making customization simple for team members who are not adept to coding syntax.

Pre-commit hooks are a simple way to check your code for any issues before committing your code to Github. It could be something as simple as removing extra spaces from the end of a file to verifying that the code you want to commit is valid Python or does not contain any secrets or access tokens. Pre-Commit Hooks can be written in a number of languages including Python, Ruby, and Rust but this automation focuses on Python.

When using Github and Jekyll it is easy to end up with files that are missing data types, with no built in way to enforce uniformity. The Jekyll-Gather-Data-Types automation creates reports that identify what data types are being used across all files in a collection and what might be missing from individual files in order to target code for remediation. Future functionality could include providing the option of using GitHub actions to prevent incomplete files from being committed (PRs).

GitHub’s Contributor’s endpoint only shows the people who put in pull requests. On cross functional teams that use GitHub to manage projects, contributions from non code contributors (Designers, Product/Project Managers, Business Analysts, Q/A testers, etc.) are represented by comments on issues. True GithHub Contributors delivers a consolidated list of who contributed and how many times. This code can be seen on Hack for LA’s project pages, where are contributors are represented by their GitHub Avatar in the Contributors section.