Backup your GitHub repositories (including issues and comments).
The backup will include a copy of the git repository itself (a bare, mirror clone), the wiki repository if there is one, all of the repository issues and comments (including the important metadata for each issue and comment and any attached files), and all of the pull requests (including TBD). All information will be written to disk for easy follow-up with e.g., tar or similar and copy to the backup medium.
We need to backup all of the release data (release title and body text -- we already have the git tags in the repository). Part of that should include any manually uploaded release artifacts (we don't care about the source tar/zip files)
I still need to do some more research on exactly what data we can get back from the API about projects, but ideally we will save both repository and organization projects as well as the columns in them, any associated automation, and any non-issue cards (as well as links/info to issues that are in the project)
I need to do some more investigation on how/what data comes back from the API and so how/where we might store it in the final backup. It could probably be it's own file branches.yml or something (or maybe be merged into the main repository.yml file but that might be getting too cluttered for easy human consumption).
We'd like to add the public ssh key bits into the backup for a given repository. I'm not sure about naming conventions or where in the backup tree structure the data might live yet. Maybe we should just add them to the repository metadata yaml file since it's just plain text data anyway...
Right now we're completely ignoring any rate limiting information from the GitHub API which is fine for small organizations or single repositories (with a low number of issues, etc). But eventually we will need to detect and recover from being rate limited. This might also include drastic actions such as sleeping for one hour to let the 5,000 API calls per hour refresh, or something more intelligent where we introduce delays during calls if we're detecting that we'll have a lot of data.
If a repository has the wiki feature enabled then we should (mirror) clone it into a wiki directory alongside the repository itself.
I'm not sure if it's possible yet or not, but if we can detect ahead of time if the wiki is empty or not then we should only do the clone if it actually has any data. (Otherwise we can probably detect that it's empty afterwards and clean it up then)
hub is a command line tool that wraps git in order to extend it with extra features and commands that make working with GitHub easier. For an official
lazyhub lazyhub - Terminal UI Client for GitHub using gocui. Demo Features ?? Check the trending repositories on GitHub today ?? Search repositories ?
goaction Package goaction enables writing Github Actions in Go. The idea is: write a standard Go script, one that works with go run, and use it as Git
A simple tool to help apply changes across many GitHub repositories simultaneously
A GitHub Action that automatically check if some link in your README.md is broken or not responding.
octotrends.com A niftly little tool I wrote to try and find repos and languages that are rapidly growing on GitHub. Growth rates are based on % growth
git-private lets you store private data inside a git repo. A common use case is protecting files containing API keys et.c.
CommentCI A tool to sent comments to Issues or Pull Requests in Github from CI tools. Usage Required environment variables: GITHUB_COMMENT_USER - User
?? Sonarqube PR Issues Review Simple Webhook for Sonarqube which publishes the issues found in the PR as review requesting changes. The only SCM that
gh is GitHub on the command line. It brings pull requests, issues, and other GitHub concepts to the terminal next to where you are already working with git and your code
go-get-collibra-backup Introduction This repository is a very simple go application that's intended, at this point, more of a demonstration about how
Backup Maker Tiny backup client packed in a single binary. Interacts with a Backup Repository server to store files, uses GPG to secure your backups e
actions-plan-preview An action that comments PipeCD's PlanPreview result on GitHub pull request. This action can be used for all application kinds: Ku
todocheck todocheck is a static code analyzer for annotated TODO comments. It let's you create actionable TODOs by annotating them with issues from an
Kstone 中文 Kstone is an etcd management platform, providing cluster management, monitoring, backup, inspection, data migration, visual viewing of etcd
News This is the under-development branch. Stay tuned for the upcoming release v12.2.0. Looking for a stable release? Head over to the v12.1.8 branch
gh contribute being a gh extension for finding issues to help with in a GitHub repository. This extension suggests an issue in a given repository to w
Linked Issue (Github Action) This action find the Issues linked in a Pull Request. It parses the HTML of the PR page to find the linked issues. Inputs
A command line utility for labeling GitHub issues and pull requests
