The .about.yml mechanism allows an project to publish and maintain metadata that can be easily maintained by project owners, that is visible and accessible to interested parties, and that can be harvested and processed by tools and automated systems.

Upload allure reports to different file storage providers

Extract release notes from your git log

GitHub Releases tasks for Capistrano v3

A cheat-sheet cli for a cheat repository

Create GitHub's compare view URLs for pull request from diff of Gemfile.lock

GitHub Status resource for Concourse

dr works with distribution-level packaging tools and helps you make and distribute your own Debian packages through your own repository. This is a super early release, certainly NOT ready for production.

Manage GitHub via Ellen.

Searches your GitHub repositores and lists the ones using end-of-life, i.e. unmaintained, software.

Commandline tool for GitHub notifications

gitarro run tests on GitHub PRs using almost any script,language or binary, it integrate easy with other tools.

Provides few more parameters to estimate quality of the GitHub project besides stars.

calculate fighting power

Gitingest is a powerful command-line tool that fetches files from GitHub repositories and generates consolidated text prompts for AI analysis. It features smart file filtering, concurrent processing, custom exclusion patterns, authentication support, and automatic rate limit handling. Perfect for creating context-rich prompts from codebases for AI assistants, documentation generation, or codebase analysis.

Visualization of your Github activity over the past year via Github API with visualizations like table, graph, stacked graph and pie chart.

Metior is a source code history analyzer that provides various statistics about a source code repository and its change over time.

CLI for GitHub

Plugin for omnifocus gem to provide github BTS synchronization. Support for Github Enterprise: In your git config, set the key github.accounts to a space separated list of github accounts. git config --global github.accounts "github myghe" For each account API and web end points and authentication information should be stored in the git config under a key matching the account. For example: git config --global github.user me git config --global github.password mypassword git config --global myghe.api https://ghe.mydomain.com/api/v3 git config --global myghe.api https://ghe.mydomain.com/ For each account can you specify the following parameters: * api - specify an API endpoint other than https://api.github.com. This is so you can point this at your Github Enterprise endpoint. * web - specify an API endpoint other than https://www.github.com. This is so you can point this at your Github Enterprise endpoint * user, password - A username and password pair for Basic http authentication.

openstudio base gem for creating generic extensions with encapsulated data and measures.