Agazelle
/
bot-replication
forked from wuxiaojun/bot-replication
0
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
bot-replication/data/apps_bot.csv

1335 lines
126 KiB
Plaintext
Raw Permalink Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

"2","4","dependabot","github","9919","Organization","Dependabot","","https://dependabot-api.githubapp.com","2019/4/16 22:34:25","2021/12/14 16:44:12","{'checks': 'write', 'contents': 'write', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'read', 'workflows': 'write'}","['check_suite', 'issues', 'issue_comment', 'label', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'repository']"
"3","5","github-actions","github","9919","Organization","GitHub Actions","Automate your workflow from idea to production","https://help.github.com/en/actions","2018/7/30 09:30:17","2019/12/10 19:04:12","{'actions': 'write', 'administration': 'read', 'checks': 'write', 'contents': 'write', 'deployments': 'write', 'discussions': 'write', 'issues': 'write', 'metadata': 'read', 'organization_packages': 'write', 'packages': 'write', 'pages': 'write', 'pull_requests': 'write', 'repository_hooks': 'write', 'repository_projects': 'write', 'security_events': 'write', 'statuses': 'write', 'vulnerability_alerts': 'read'}","['branch_protection_rule', 'check_run', 'check_suite', 'create', 'delete', 'deployment', 'deployment_status', 'discussion', 'discussion_comment', 'fork', 'gollum', 'issues', 'issue_comment', 'label', 'milestone', 'page_build', 'project', 'project_card', 'project_column', 'public', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'push', 'registry_package', 'release', 'repository', 'repository_dispatch', 'status', 'watch', 'workflow_dispatch', 'workflow_run']"
"4","8","renovate","renovatebot","38656520","Organization","Renovate","![header](https://app.renovatebot.com/images/whitesource_renovate_660_220.jpg)
## Automated Dependency Updates
[WhiteSource Renovate](https://renovate.whitesourcesoftware.com) keeps source code dependencies up-to-date using automated Pull Requests. It will scan repositories for package manager files (e.g. from npm/Yarn, Bundler, Composer, Go Modules, Pip/Pipenv/Poetry, Maven/Gradle, Dockerfile/k8s, and many more), and submit Pull Requests with updated versions whenever they are found.
This app is free to install for both public and private repositories. Service is provided complimentary of WhiteSource and no paid plan is required.
### Intelligent, helpful onboarding
![Onboarding](https://docs.renovatebot.com/assets/images/onboarding.png)
Install WhiteSource Renovate risk-free and you'll first receive an onboarding Pull Request in each repository. It analyzes the repository files and describes what will happen next, so there's no surprises.
### Unopinionated, highly flexible configuration
```json
{
""rangeStrategy"": ""pin"",
""ignorePaths"": [""examples/**""],
""packageRules"": [{
""packagePatterns"": [""^angular.*""],
""groupName"": ""angular"",
""automerge"": true
}]
}
```
Modify any of Renovate's smart defaults with custom overrides at the repository, package file, dependency type, and package levels.
### Support for monorepo directory structures
WhiteSource Renovate will scan all files in each repository to look for relevant package files. It will also group upgrades from the same monorepo into a single PR to ensure tests pass and PR noise is reduced. Natively supports Lerna and Yarn Workspaces with zero configuration necessary.
It is also works fine with a mix of package managers / languages within the same repository.
### Automatic lock file and checksum support
WhiteSource Renovate will generate updated lock files such as `package-lock.json` or `yarn.lock` if you're already using them. It will also automatically resolve any conflicts after merges.
### Ease the noise with custom schedules
```json
{
""timezone"": ""America/New_York"",
""schedule"": ""before 5am every weekday"",
""lockFileMaintenance"": {
""enabled"": true,
""schedule"": ""after 10pm on sunday""
},
""packageRules"": [{
""packageNames"": [""aws-sdk""],
""schedule"": ""before 5am every wednesday""
}]
}
```
Throttle updates however you want with schedules, configurable right down to the per-package level.
### Rules-based automerging
![automerging](https://docs.renovatebot.com/assets/images/automerged-pr.png)
Merge some updates without human intervention if they pass tests and satisfy your automerge rules.","https://renovate.whitesourcesoftware.com","2017/6/2 07:04:12","2020/12/15 14:14:01","{'administration': 'read', 'checks': 'write', 'contents': 'write', 'emails': 'read', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write', 'vulnerability_alerts': 'read', 'workflows': 'write'}","['check_run', 'issues', 'issue_comment', 'pull_request', 'push', 'repository', 'status']"
"5","9","vercel","vercel","14985020","Organization","Vercel","Vercel for GitHub automatically deploys your PRs to Vercel.
Preview every PR live, without any configuration required.
For more information, see our [documentation](https://vercel.com/docs/github?utm_source=github&utm_medium=marketplace&utm_campaign=vercel-app).
![](https://assets.vercel.com/image/upload/v1597943727/front/github/github-comment.png)","https://vercel.com/github","2018/1/19 21:51:06","2020/12/22 19:45:55","{'administration': 'write', 'checks': 'write', 'contents': 'write', 'deployments': 'write', 'emails': 'read', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'repository_hooks': 'write', 'statuses': 'write'}","['deployment', 'pull_request', 'push']"
"6","10","azure-pipelines","AzurePipelines","39924718","User","Azure Pipelines","### Continuously build, test, and deploy to any platform and cloud
[Azure Pipelines](https://azure.microsoft.com/services/devops/pipelines/) offers cloud-hosted pipelines for Linux, macOS, and Windows with 10 free parallel jobs and unlimited minutes for open source projects.
:v: **Any language, platform, and cloud**
Build, test, and deploy Node.js, Python, 
Java, PHP, Ruby, Go, C/C++, C#, Android, and iOS apps. Run in parallel on Linux, macOS, and Windows. Deploy to cloud providers like Azure, AWS, and GCP. Distribute mobile apps through beta channels and app stores.
:whale2: **Native container support**
Create new containers with ease and push them to any registry. Deploy containers to independent hosts or Kubernetes.
:muscle: **Advanced workflows and features**
Easy build chaining and multi-phased builds. Support for YAML, test integration, release gates, reporting, and more.
:wrench: **Extensible**
Use a range of build, test, and deployment tasks built by the community – hundreds of extensions from Slack to SonarCloud. You can even deploy from other CI systems, like Jenkins. Webhooks and REST APIs help you integrate.
:blue_heart: **Free, to you from Azure Pipelines**
Free cloud-hosted builds for public and private repositories.
","https://azure.microsoft.com/services/devops/pipelines/","2018/2/23 17:14:32","2018/10/25 18:51:25","{'checks': 'write', 'contents': 'write', 'deployments': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['check_suite', 'create', 'issue_comment', 'pull_request', 'push', 'release', 'repository']"
"7","11","allcontributors","all-contributors","46410174","Organization","AllContributors","✨ Recognize all contributors, not just the ones who push code
> Use the project README (or other prominent public documentation page in the project) to recognize the contributions of members of the project community.
The [@all-contributors bot](https://github.com/all-contributors/all-contributors-bot) automatically adds contributor acknowledgements according to the all-contributors specification ✨
## Usage:
Comment on an issue or pull request with:
`@all-contributors please add @jakebolam for infrastructure, tests and code`","https://github.com/all-contributors/all-contributors-bot","2019/1/7 12:57:03","2021/1/29 20:21:27","{'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['issue_comment']"
"8","12","lock","dessant","7513068","User","Lock","⚠️ **This app is no longer maintained, please migrate to [Lock Threads](https://github.com/dessant/lock-threads).**
A GitHub App that locks closed issues and pull requests after a period of inactivity.
![](https://raw.githubusercontent.com/dessant/lock-threads-app/master/assets/screenshot.png)
## Usage
1. **[Install the GitHub App]()** for the intended repositories
2. Create `.github/lock.yml` based on the template below
3. It will start scanning for closed issues and/or pull requests within an hour
**If possible, install the app only for select repositories. Do not leave the `All repositories` option selected, unless you intend to use the app for all current and future repositories.**
#### Configuration
Create `.github/lock.yml` in the default branch to enable the app, or add it at the same file path to a repository named `.github`. The file can be empty, or it can override any of these default settings:
```yaml
# Configuration for Lock Threads - https://github.com/dessant/lock-threads-app
# Number of days of inactivity before a closed issue or pull request is locked
daysUntilLock: 365
# Skip issues and pull requests created before a given timestamp. Timestamp must
# follow ISO 8601 (`YYYY-MM-DD`). Set to `false` to disable
skipCreatedBefore: false
# Issues and pull requests with these labels will be ignored. Set to `[]` to disable
exemptLabels: []
# Label to add before locking, such as `outdated`. Set to `false` to disable
lockLabel: false
# Comment to post before locking. Set to `false` to disable
lockComment: >
This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.
# Assign `resolved` as the reason for locking. Set to `false` to disable
setLockReason: true
# Limit to only `issues` or `pulls`
# only: issues
# Optionally, specify configuration settings just for `issues` or `pulls`
# issues:
# exemptLabels:
# - help-wanted
# lockLabel: outdated
# pulls:
# daysUntilLock: 30
# Repository to extend settings from
# _extends: repo
```
","https://github.com/dessant/lock-threads-app","2017/11/12 10:50:45","2021/7/4 16:53:29","{'metadata': 'read', 'single_file': 'read'}","[]"
"9","13","imgbot","imgbot","80986210","Organization","Imgbot","Imgbot is a friendly robot that optimizes your images and saves you time. Optimized images mean smaller file sizes without sacrificing quality.
Shortly after installing Imgbot, you will receive a pull request with all of your images optimized. Just merge the pull request and you’re done! As you work on your project, Imgbot works alongside you to keep your images optimized.
*Imgbot uses lossless compression by default.*
## Why should I optimize my images?
When you’re shipping code and hitting deadlines, it’s easy to forget about optimizing your images. But the truth is, if you don’t optimize your images you are losing money. Web pages with optimized images load faster. Faster pages have higher conversion rates, lower bounce rates, and happier users. And of course, smaller images reduce bandwidth costs for you and your visitors.
## Why should I use Imgbot?
Setting up and configuring your own tools can be a complicated and lengthy process. That means you are not focusing on shipping your next big update. With just a few clicks, you can install Imgbot and permanently solve your image optimization problems.
Imgbot is verified by GitHub which mean it has gone through extensive [security reviews](https://tinyurl.com/yyskcvr2) to make sure Imgbot is reliable and your data is safe. You can trust Imgbot.","https://imgbot.net","2017/8/24 04:59:23","2021/8/13 17:17:44","{'contents': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['push']"
"10","14","mergify","Mergifyio","37838584","Organization","Mergify","Pull requests automation service.","https://mergify.io","2018/3/30 10:19:51","2021/11/3 14:34:07","{'administration': 'read', 'checks': 'write', 'contents': 'write', 'emails': 'read', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pages': 'write', 'pull_requests': 'write', 'statuses': 'read', 'workflows': 'write'}","['check_run', 'check_suite', 'issue_comment', 'member', 'membership', 'organization', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'push', 'repository', 'status', 'team', 'team_add']"
"11","15","pre-commit-ci","pre-commit-ci","64617429","Organization","pre-commit ci","","https://pre-commit.ci","2020/6/13 00:09:59","2021/2/9 03:29:46","{'contents': 'write', 'issues': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write', 'workflows': 'write'}","['issue_comment', 'pull_request', 'push', 'repository']"
"12","16","review-notebook-app","ReviewNB","43564320","Organization","Review Notebook App","Having trouble using Jupyter Notebooks in your team? Version control, code reviews and collaboration is difficult with Jupyter Notebooks.
ReviewNB provides a complete code review workflow for Jupyter Notebooks on GitHub.
- [Visual diff ](https://tinyurl.com/yxvokoew) for every GitHub commit or Pull Request containing Notebooks
- [Commenting](https://tinyurl.com/y648jktr) on the Notebook diff to review Jupyter Notebook PRs.
- You can ask clarifying questions, suggest improvements & open/close issues before approving the PR.
- (Coming Soon) A CI pipeline for Jupyter Notebooks to continuously test each change. See [treon](https://github.com/ReviewNB/treon), our open source library for notebook testing.
Our aim is to make Notebooks a first class entity in Data Science & ML teams. More details [on our website](https://www.reviewnb.com/).
#### Visual Diff
![HTML Diff](https://uploads-ssl.webflow.com/5ba4ebe021cb91ae35dbf88c/5ba93ded243329a486dab26e_sl-code%2Bimage.png)","https://www.reviewnb.com/","2018/8/1 10:30:07","2020/5/28 09:46:02","{'contents': 'read', 'emails': 'read', 'metadata': 'read', 'pull_requests': 'write'}","['pull_request']"
"13","17","sentry-io","getsentry","1396951","Organization","Sentry.io","Sentry is an error tracking and monitoring tool that aggregates errors across your stack in real time.
#### Integrate GitHub into your Sentry workflow
Sentry's GitHub integration unlocks enhanced release tracking with files changed and author details, informative deploy emails, and suggested assignees for new errors. Route alerts to the right person based on the GitHub commit that caused the issue, cutting remediation time to five minutes.
Create and link Sentry issue groups directly to a GitHub issue or pull request in any of your repositories, providing a quick way to jump from Sentry bug to tracked issue or PR!
#### Installation Notes
* It's recommended to install the Sentry GitHub app from your Sentry Integration settings. You may install the app here, however you will need to be a **Manager** or **Owner** of your Sentry organization to fully configure the integration.
* Once this app is installed on a GitHub organization or account and is associated to a Sentry organization, that particular GitHub organization or account **cannot be associated with any other Sentry organization**.","https://sentry.io","2018/5/24 21:42:15","2021/2/26 16:54:26","{'administration': 'read', 'contents': 'read', 'emails': 'read', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'repository_hooks': 'write'}","['pull_request', 'push']"
"14","18","bors","bors-ng","24979321","Organization","bors","* [Home]
* [Forum]
* [Docs]
* [Log into dashboard]
[Home]: https://bors.tech/
[Log into dashboard]: https://app.bors.tech/
[Docs]: https://bors.tech/documentation/getting-started/
[Forum]: https://forum.bors.tech/
______
Bors-NG (the Next-Generation implementation of “bors”) is a GitHub App that automates a <a href=""http://graydon2.dreamwidth.org/1597.html"" title=""The not-rocket-science rule of software engineering"">“common sense” workflow</a> for software development on GitHub: merge a pull request and master together, run the test suite, then push the merged whole up into the master branch. This means that whatever is in master branch has passed the tests, no matter what, even if there are <a href=""https://bors.tech/essay/2017/02/02/pitch/"" title=""Semantic conflicts"">subtle interactions</a> between different pull requests.
This instance is available to anybody with a public GitHub repository. Private repositories will be silently ignored.","https://bors.tech/","2017/3/23 19:10:13","2018/2/1 21:55:15","{'checks': 'write', 'contents': 'write', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pages': 'write', 'pull_requests': 'write', 'statuses': 'write', 'workflows': 'write'}","['check_run', 'check_suite', 'issue_comment', 'member', 'membership', 'organization', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'repository', 'status', 'team']"
"15","19","weekly-digest","abhijeetps","20141002","User","Weekly Digest","> App built using [Probot](https://probot.github.io/) which generates an automated summary of activities and happening on your GitHub repository.
## App in Action ##
![A Weekly Digest generated by app.](https://user-images.githubusercontent.com/20141002/41304450-d2bc9234-6e8d-11e8-965d-649ed2d04651.gif)
## Features ##
When the Weekly Digest App gets installed in a repository of a user or organization, it curates together the following data and publishes it as an issue:
- Issues created in the last one week
- Open Issues
- Closed Issues
- Noisy Issue
- Liked Issue
- Pull requests opened, updated, or merged in the last pull request
- Opened Pull Requests
- Updated Pull Requests
- Merged Pull Requests
- Commits made in the master branch, in the last week
- Contributors, adding contributions in the last week
- Stargazers, or the fans of your repositories, who really loved your repo
- Releases, of the project you are working on
The app, as the name suggests, generates these digests and publishes it on weekly basis, typically on a Sunday.
One can change the default configuration of the app by adding a _.github/weekly-digest.yml_ file in their GitHub repository, which allows them to configure the publish day and the specific information included in the digest.","https://github.com/probot/weekly-digest","2018/5/22 00:18:40","2018/8/6 17:42:35","{'contents': 'read', 'deployments': 'read', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'single_file': 'write'}","['commit_comment', 'create', 'delete', 'deployment', 'deployment_status', 'fork', 'gollum', 'issues', 'issue_comment', 'label', 'milestone', 'public', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'push', 'release', 'repository', 'watch']"
"16","20","msftbot","microsoftfabricbot","48299081","Organization","msftbot","Microsoft GitHub Bot, powered by Fabric Bot Services.
Microsoft employees, please email fabricbotservices@microsoft.com for any enquiries. Please access https://aka.ms/fabricbotdocs for more information.
Please kindly be advised that you need to be officially onboarded in-order for your GitHub repo to benefit from bot-services - merely installing the app will not bring about any automation.","https://aka.ms/fabricbotconfig","2019/3/8 02:24:22","2021/7/19 20:47:42","{'checks': 'write', 'contents': 'write', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'organization_projects': 'write', 'pull_requests': 'write', 'repository_projects': 'write', 'statuses': 'write'}","['check_suite', 'issues', 'issue_comment', 'project_card', 'pull_request', 'pull_request_review', 'release', 'status']"
"17","21","todo","JasonEtco","10660468","User","todo","A GitHub App built with [Probot](https://github.com/probot/probot) that creates new issues based on actionable comments in your code.
## Usage
Using **todo** should be really simple. Once you've installed it in your repository, simply push some code (to your default branch, a PR; doesn't matter). If the code you pushed includes the configured keyword (default is `@todo`), then the integration will create a new issue for you using the comment your wrote in your code!
If I pushed this:
```js
/**
* @todo Take over the world
* @body Humans are weak; Robots are strong. We must cleans the world of the virus that is humanity.
*/
function ruleOverPunyHumans () {
// We must strategize beep boop
}
```
**todo** would create a new issue:
![todo](https://user-images.githubusercontent.com/10660468/31048765-83569c30-a5f2-11e7-933a-a119d43ad029.png)
**Note:** While the above example is in Javascript, **todo** has been tested in JS, Go, C, C# and Ruby, and should work in any language.
## Behaviour in pull requests
To reduce noise and keep your **todo** notes in the right context, **todo** comments made in commits that are part of a pull request will be converted into comments on that pull request. When the PR is merged, **todo** will determine which of those **todo**s have yet to be resolved and open an appropriate issue.
## Configuring for your project
There are a couple of configuration options in case you need to change the default behaviour. Note that the defaults are likely fine for most projects, so you might not need to change them.
Add a `todo` object in your `.github/config.yml` file like this:
```yml
todo:
keyword: ""@makeAnIssue""
```
You can learn more about the configuration options available on [the GitHub repo](https://github.com/jasonetco/todo).","https://todo.jasonet.co","2017/9/28 01:20:32","2018/2/13 06:08:27","{'contents': 'read', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['pull_request', 'push']"
"18","22","copybara-service","copybara-github","32201506","User","Copybara-Service","This is an helper app for Google Copybara, synchronizing repositories maintained by Google.","http://copybara.io","2019/10/18 20:47:54","2019/11/4 17:07:31","{'actions': 'write', 'administration': 'write', 'checks': 'write', 'contents': 'write', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write', 'workflows': 'write'}","['check_run', 'check_suite', 'commit_comment', 'create', 'delete', 'issues', 'issue_comment', 'label', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'push', 'release', 'status']"
"19","23","depfu","depfu","21121772","Organization","Depfu","[![Depfu](https://depfu.com/images/gh_app_header.png)](https://depfu.com)
**Depfu is like a colleague who sends you super nice pull requests with all the info you need about an update. You stay in control if and when to merge.**
We support all Ruby projects using Bundler and all JS projects using npm or Yarn.
## Installation instructions and documentation
Check out the [docs](https://depfu.com/docs) for installation instructions as well as details about how everything works. If anything is unclear or you have more questions, send us an [email](mailto:hi@depfu.com) and we'll get back to you right away!
## Plans and pricing
Depfu is free for Open Source. For private repos please take a look at our [pricing](https://depfu.com/pricing).
---","https://depfu.com","2016/11/24 09:25:59","2019/5/24 16:41:59","{'checks': 'read', 'contents': 'write', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'read', 'vulnerability_alerts': 'read'}","['check_run', 'check_suite', 'delete', 'issues', 'issue_comment', 'pull_request', 'pull_request_review', 'push', 'repository', 'status']"
"20","24","deepsource-autofix","deepsourcelabs","40287229","Organization","DeepSource Autofix","DeepSource's Autofix app is used for generating pull-requests for autofixes to issues in your code from DeepSource.","https://deepsource.io","2020/3/11 07:23:11","2021/8/25 13:21:23","{'contents': 'write', 'metadata': 'read', 'pull_requests': 'write'}","[]"
"21","25","transifex-integration","transifex","22542","Organization","Transifex Integration","Seamlessly connect and integrate your GitHub repositories to your Transifex projects. Once integrated:
- New localization files from your GitHub repository will be automatically added to your Transifex project, and
- Fully translated content from your Transifex project will be automatically pushed back to your GitHub repository (via commit or Pull Request, depending on which you select).
All setup is easily managed through the all-in-one Transifex web app, in three simple steps:
1. Authenticate Transifex on GitHub,
1. Link your GitHub repository to a Transifex project, and
1. Specify the files you'd like to sync, and what automated actions should take place after localized content is sent from Transifex back to Github.
**Support your files, whatever the format**
The Transifex platform supports 30+ File Formats (po, .strings, .srt,to name a few). Find a comprehensive list of all supported file formats in the [Transifex Help Center](https://docs.transifex.com/formats/introduction).
**Leverage the full suite of localization tools**
Take full advantage of all the localization tools available in the Transifex platform from Translation Memory, Glossary, and Machine Translation to help manage translation quality and consistency; to customized workflows and collaboration tools to connect your translators, community, or professional translation vendors; and more.
**Install in 4 simple steps**
1. If you are installing from Transifex, visit Organization Settings > Manage Integrations.
1. Click Install GitHub, Transifex app to install GitHub Integration to your GitHub account.
1. Select the GitHub repositories that you want to make available for your localization projects.
1. Head back to the Transifex platform and authorize the GitHub Integration for your Transifex organization.
Sit back and watch the integration automatically push content and translations!
","https://www.transifex.com","2018/10/5 11:32:40","2019/2/6 15:02:58","{'administration': 'read', 'contents': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['push']"
"22","26","dotnet-maestro","dotnet","9141961","Organization","DotNet Maestro","","https://maestro-prod.westus2.cloudapp.azure.com/","2018/8/27 17:31:43","2020/6/25 19:36:57","{'checks': 'write', 'contents': 'write', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'read'}","[]"
"23","27","whitesource-for-github-com","whitesource","1539627","Organization","WhiteSource for GitHub.com","WhiteSource for GitHub.com is a GitHub app which continuously scans all your repos, detects vulnerabilities in open source components and provides fixes. It supports both private and public repositories, to make sure nothing puts your product at risk.
We've got you covered with over 200 programming languages support and continuous tracking of multiple open source vulnerabilities databases like the NVD and additional security advisories.
### Find & Fix Vulnerable Open Source Libraries
WhiteSource will scan your repos every time you apply a push and will open an issue for every vulnerable open source library dependency the minute it is added. The issue will provide you with reference links, a dependency tree (if it exists), vulnerability information, and suggested fixes.
![screenshot](https://whitesource-resources.whitesourcesoftware.com/vulnerability_ws_for_gh_com.png)
### Using GitHub Checks in WhiteSource for GitHub.com
WhiteSource will scan your repository as part of GitHub Checks whenever a commit is pushed to the repository. If one or more vulnerabilities were found, a report with all the new vulnerabilities will be presented. You can prevent merging pull requests in case vulnerabilities were found and the check resulted in a failure.
### Getting Started
Read our [documentation](https://whitesource.atlassian.net/wiki/spaces/WD/pages/697696422/WhiteSource+for+GitHub.com) for guidance and how to use the app. ","https://www.whitesourcesoftware.com","2019/5/15 16:40:55","2019/9/22 05:37:45","{'administration': 'read', 'checks': 'write', 'contents': 'write', 'deployments': 'read', 'emails': 'read', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'organization_hooks': 'read', 'organization_projects': 'write', 'pages': 'write', 'pull_requests': 'write', 'repository_hooks': 'read', 'repository_projects': 'write', 'statuses': 'write', 'vulnerability_alerts': 'read', 'workflows': 'write'}","['issues', 'member', 'membership', 'organization', 'pull_request', 'push', 'team', 'team_add']"
"24","28","open-collective-bot","opencollective","13403593","Organization","Open Collective Bot","Open Collective Bot helps you promote your Open Collective inside your GitHub repository. Whenever an issue is marked complete, it will create a comment suggesting a donation.","https://github.com/opencollective/opencollective-bot","2019/1/16 08:50:59","2019/3/6 16:47:16","{'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['issues', 'pull_request']"
"25","29","codesee-architecture-diagrams","Codesee-io","59343751","Organization","CodeSee Architecture Diagrams","CodeSee creates a visual map of your codebase that stays up to date with every PR. Visualize your whole codebase, see generated insights, and share a single, accurate source of truth to help quickly onboard new contributors.
CodeSee Maps uses GitHub to generate dependencies between files and update your map to reflect changes in your codebase.
We do not store your code, your code is only stored by GitHub. We analyze your code while it's on GitHub's servers using a GitHub Action.
See [our docs](https://docs.codesee.io/en/latest/installation/#permissions) for more information on why we request these permissions.","https://www.codesee.io","2021/6/22 20:15:02","2021/10/12 04:40:24","{'actions': 'write', 'administration': 'read', 'contents': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'workflows': 'write'}","['pull_request']"
"26","30","forking-renovate","renovateapp","32241687","Organization","Forking Renovate","![header](https://renovatebot.com/images/design/header_small.jpg)
""Forking Renovate"" is the sister app to [Renovate Bot](https://github.com/apps/renovate). The difference is that Forking Renovate operates using forks of repositories instead of as a collaborator, so needs only read-only permissions rather than read-write. It works on public (e.g. open source) repositories only.
Please see the Renovate Bot page and documentation for further details.","https://renovatebot.com","2017/12/12 14:15:11","2021/9/9 20:00:18","{'administration': 'read', 'contents': 'read', 'deployments': 'read', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['issues', 'public', 'pull_request', 'push']"
"27","31","restyled-io","restyled-io","31419072","Organization","Restyled.io","Nudge your team toward consistent style with every Pull Request.","https://restyled.io","2017/10/10 21:47:29","2019/3/23 13:07:29","{'contents': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['pull_request', 'repository']"
"28","32","cla-bot-2020","cla-bot-2020-test-org","62056778","Organization","cla-bot-2020","contributor license agreement bot","https://cla-bot-2020.parity.io","2020/2/5 15:01:04","2020/6/15 14:53:14","{'administration': 'write', 'checks': 'write', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'organization_hooks': 'write', 'pull_requests': 'write', 'repository_hooks': 'write', 'statuses': 'write'}","['check_run', 'check_suite', 'issues', 'member', 'organization', 'public', 'pull_request', 'repository']"
"29","33","whitesource-bolt-for-github","whitesource","1539627","Organization","WhiteSource Bolt for GitHub","We'll help you harness the power of open source without compromising on security or agility!
WhiteSource Bolt for GitHub is a FREE app, which continuously scans all your repos, detects vulnerabilities in open source components and provides fixes. It supports both private and public repositories, to make sure nothing puts your product at risk.
We've got you covered with over 200 programming languages support and continuous tracking of multiple open source vulnerabilities databases like the NVD and additional security advisories.
### Find & Fix Vulnerable Open Source Libraries
WhiteSource will scan your repos every time you apply a push (you are limited to 5 scans a day per repo) and will open an issue for every vulnerable open source library dependency the minute it is added. The issue will provide you with reference links, a dependency tree (if it exists), vulnerability information, and suggested fixes.
![screenshot](https://www.whitesourcesoftware.com/wp-content/uploads/2018/12/Vulnerability_issue_closed.png)
### Using GitHub Checks in WhiteSource Bolt
WhiteSource will scan your repository as part of GitHub Checks whenever a commit is pushed to the repository. If one or more vulnerabilities were found, a report with all the new vulnerabilities will be presented. You can prevent merging pull requests in case vulnerabilities were found and the check resulted in a failure.
### Your Language, Your Tools
We support over 200 programming languages, and we cover all common package managers – so we got you fully covered. Check out [our language page](https://www.whitesourcesoftware.com/whitesource-languages/) for more details.
### Most Comprehensive Vulnerability Coverage
Our database provides the largest coverage of vulnerability listings from multiple databases including the CVE/NVD, GitHub issue tracker, a wide range of security advisories, and popular open source projects issue trackers.
### Getting Started
Read our [documentation](https://whitesource.atlassian.net/wiki/spaces/WD/pages/556007950/WhiteSource+Bolt+for+GitHub) for guidance and how to use the app.
You can also visit our Frequently Asked Questions page [here](https://bolt.whitesourcesoftware.com/github/faq/).
### Looking for A More Advanced Solution?
Contact us to learn more about our full open source security and license compliance platform. <b>[Start Your Free Trial Today](https://whitesourcesoftware.com/trial3/)</b>.","https://bolt.whitesourcesoftware.com/github/","2018/8/29 21:10:23","2019/6/2 11:14:06","{'administration': 'read', 'checks': 'write', 'contents': 'write', 'deployments': 'read', 'emails': 'read', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'organization_hooks': 'read', 'organization_projects': 'write', 'pages': 'write', 'pull_requests': 'write', 'repository_hooks': 'read', 'repository_projects': 'write', 'statuses': 'write', 'vulnerability_alerts': 'read'}","['issues', 'member', 'membership', 'organization', 'pull_request', 'push', 'team', 'team_add']"
"30","34","google-cloud-policy-bot","dpebot","19979279","User","Google Cloud Policy Bot","Scan a repository, and track compliance to a pre-configured set of rules. *This is a Google-only bot, and will not work on a general repository*.","https://github.com/googleapis/repo-automation-bots/","2021/3/18 03:01:16","2021/3/22 17:41:35","{'administration': 'read', 'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'secret_scanning_alerts': 'read', 'security_events': 'read'}","[]"
"31","35","microsoft-github-operations","microsoft","6154722","Organization","Microsoft GitHub Operations","This GitHub App is used to manage compliance, self-service configuration, and other specific tools for a specific set of organizations.
## Operations
This app is used for important operations.
## Management
This GitHub App is managed by the One Engineering System (1ES) team at Microsoft.","https://github.com/microsoft#appoperations","2019/9/24 02:44:55","2020/11/19 20:31:32","{'administration': 'write', 'contents': 'write', 'issues': 'write', 'members': 'write', 'metadata': 'read', 'organization_administration': 'write', 'organization_hooks': 'write', 'organization_plan': 'read', 'organization_user_blocking': 'write', 'pull_requests': 'write', 'repository_hooks': 'write'}","['fork', 'member', 'membership', 'organization', 'org_block', 'public', 'repository', 'star', 'team', 'team_add', 'watch']"
"32","36","sync-by-unito","unitoio","13460182","Organization","Sync by Unito","### **Build the GitHub workflow you need**
Unito goes beyond your typical integration tool, allowing you to build entire workflows across tools, teams, and organizations. All Unito integrations offer two-way sync, meaning essential information can flow back and forth between the tools you love.
Be more productive and ease collaboration between your teams. Unito’s GitHub integration syncs:
- Title
- Description
- Comments
- State
- Milestones
- Issue number
- Labels
- Issue type
- and more
**Collaborate with non-technical teams**
Triage development requests from tools like Asana, Trello, or Wrike, provide visibility into progress, give and receive feedback, and more, all from within GitHub.
**Create a high-level roadmap of development projects**
Create a high-level roadmap in tools like Trello or Wrike to better organize your development work and to provide executive oversight and company-wide visibility.
### Get the Unito GitHub integration
To get started, [head over to the Unito app](https://app.unito.io/#/signup?utm_source=github&utm_medium=marketplace&utm_campaign=github-unito) and we'll walk you through the rest.
### Learn more & get support
- Learn more about [Unito’s GitHub integration](https://unito.io/github-sync/?utm_source=github&utm_medium=marketplace&utm_campaign=github-unito)
- [Talk to a member of our team](https://unito.io/contact/?utm_source=github&utm_medium=marketplace&utm_campaign=github-unito).","https://unito.io/?utm_source=github&utm_medium=marketplace&utm_campaign=github-unito","2020/5/8 14:51:59","2020/5/21 21:06:12","{'emails': 'read', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'organization_hooks': 'read', 'organization_projects': 'write', 'pull_requests': 'write', 'repository_hooks': 'write', 'repository_projects': 'write'}","[]"
"33","37","release-please","dpebot","19979279","User","Release Please","A GitHub App that proposes releases based on semantic version commits defined by conventionalcommits.org.","https://github.com/googleapis/repo-automation-bots","2019/9/9 18:39:06","2019/10/15 21:23:07","{'checks': 'write', 'contents': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['pull_request', 'push', 'release']"
"34","38","gitlocalize-app","gitlocalize","25833116","Organization","GitLocalize App","A localization tool for documentations on GitHub repo","https://gitlocalize.com","2019/9/13 09:29:32","2019/9/26 12:56:09","{'contents': 'write', 'emails': 'read', 'metadata': 'read', 'pull_requests': 'write', 'repository_hooks': 'write'}","['public', 'pull_request', 'push', 'repository']"
"35","39","repo-ranger","reporanger","52087075","Organization","Repo Ranger","> A sidekick for GitHub repository maintainers
Ranger provides maintainers a set of fire-and-forget tools to automate common repository maintenance tasks, like closing issues, merging pull requests, and creating typical comments.
It is also easy to configure your own automated actions, all through through a simple YAML file.
Check out [the docs](https://reporanger.com/docs) for more information on using and configuring Ranger. ","https://reporanger.com","2018/5/8 02:48:44","2019/9/3 16:30:29","{'checks': 'read', 'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'single_file': 'write', 'statuses': 'read'}","['check_run', 'check_suite', 'commit_comment', 'issues', 'issue_comment', 'label', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'status']"
"36","40","meeseeksdev","MeeseeksBox","23667696","Organization","Meeseeksdev","Meeseeksdev bot that responds to commands, backport Pull-Request, give fine grained permissions to users. In progress. Mostly developed for the Jupyter/IPython team cross-repository/cross-organisation workflow.","https://meeseeksbox.github.io","2016/12/9 23:14:22","2018/8/28 22:29:52","{'administration': 'read', 'contents': 'write', 'deployments': 'write', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'organization_projects': 'read', 'pages': 'write', 'pull_requests': 'write', 'repository_projects': 'read', 'statuses': 'read'}","['commit_comment', 'issues', 'issue_comment', 'pull_request', 'pull_request_review', 'pull_request_review_comment']"
"37","41","kodiakhq","chdsbd","1929960","User","kodiakhq","An app to intelligently merge pull requests.
The goal of this project is to automatically update and merge PRs in a way that reduces spurious CI jobs. PRs are only updated once prior to merge, reducing CI load.","https://kodiakhq.com/","2019/4/17 23:39:48","2020/3/4 04:05:05","{'administration': 'read', 'checks': 'write', 'contents': 'write', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'read', 'workflows': 'write'}","['check_run', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'pull_request_review_thread', 'push', 'status']"
"38","42","dependencies","dependencies-io","28538687","Organization","Dependencies","Dependencies.io provides automatic updates for your dependencies via pull requests. Everything runs in a highly configurable environment (similar other CI services you're used to) so that you can fully customize your dependency update process.","https://dependencies.io","2017/5/8 18:44:41","2020/3/23 18:49:09","{'administration': 'read', 'contents': 'write', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write'}","['create', 'delete', 'membership', 'organization', 'public', 'push', 'repository', 'team', 'team_add']"
"39","43","openshift-ci","openshift","792337","Organization","OpenShift CI","The OpenShift CI system integrates with GitHub to provide pull request authors with a performant and scalable solution to testing their code, whether it be part of the OpenShift Container Platform or an application layered on top.","https://www.openshift.com/","2020/12/3 14:13:46","2020/12/16 22:35:50","{'actions': 'write', 'administration': 'write', 'checks': 'write', 'contents': 'write', 'deployments': 'write', 'issues': 'write', 'members': 'write', 'metadata': 'read', 'organization_administration': 'write', 'organization_hooks': 'write', 'organization_plan': 'read', 'organization_projects': 'admin', 'organization_secrets': 'write', 'organization_self_hosted_runners': 'write', 'organization_user_blocking': 'write', 'packages': 'write', 'pages': 'write', 'pull_requests': 'write', 'repository_hooks': 'write', 'repository_projects': 'admin', 'secrets': 'write', 'security_events': 'write', 'statuses': 'write', 'team_discussions': 'write', 'vulnerability_alerts': 'read', 'workflows': 'write'}","['check_run', 'check_suite', 'code_scanning_alert', 'commit_comment', 'create', 'delete', 'deployment', 'deployment_status', 'deploy_key', 'fork', 'issues', 'issue_comment', 'label', 'member', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'push', 'release', 'status']"
"40","44","exalate-issue-sync","Exalate-team","46967126","Organization","Exalate Issue Sync","Exalate is the most complete & flexible synchronization tool on the planet for issue trackers and task management systems such as Github, HP ALM and Jira.
With the Exalate sync tool you can experience an intuitive collaboration between teams using Jira and Github by synchronizing issue data automatically across your instances.
More details
Exalate provides a flexible synchronization engine such that issues are automatically and securely synced - between Github and Jira - wherever hosted.
We understand teams work differently over different departments and companies. Benefit from a unified view and integrated workflow! No need to adapt workflows for all teams.
With Exalate you control exactly what you share and who you share it with. Thus keeping confidential information private and secure.
Some properties
- Choose whether to sync data in both directions or unidirectionally
- Sync all data, including labels and comments
- Each party defines what is private or shared
- Sync issues out of the box
- Adapt to your needs with a flexible scripting engine
- Cut delays with instant synchronization
- You can integrate not only GitHub and Jira. Exalate supports other issue trackers such as HP QC/ALM or other. Expand your network through Exalate.
Book a demo [here](https://www.idalko.com/exalate-book-demo), or consult our [documentation](https://docs.idalko.com/exalate)
Looking for your Exalate Console URL? Find it here: https://connect.exalate.net/github/find","https://www.idalko.com/exalate","2018/10/3 09:15:33","2021/7/16 14:54:05","{'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['issues', 'issue_comment', 'pull_request', 'pull_request_review', 'pull_request_review_comment']"
"41","45","first-timers","hoodiehq","1888826","Organization","First Timers","[![Uptime Robot status](https://img.shields.io/uptimerobot/status/m779426128-6b6e81ed8dc987db17d4cad2.svg)](https://stats.uptimerobot.com/LZ40Lcoj4)
Create beautiful issues for first-time Open Source contributors – automagically ✨ based on hidden branches. See instructions at https://github.com/hoodiehq/first-timers-bot","https://github.com/hoodiehq/first-timers-bot","2017/8/30 00:37:12","2020/8/7 15:43:09","{'contents': 'write', 'issues': 'write', 'metadata': 'read'}","['create']"
"42","46","community-tc-integration","taskcluster","6257436","Organization","Community-TC Integration","Integration with the Community-TC deployment at https://community-tc.services.mozilla.com/. Add this app to the repositories for which you would like to run tasks in Taskcluster.","https://community-tc.services.mozilla.com","2019/9/11 01:15:34","2019/9/26 17:48:07","{'administration': 'read', 'checks': 'write', 'contents': 'read', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['pull_request', 'push', 'release']"
"43","47","ionitron-bot","Ionitron","6591344","User","Ionitron Bot","This bot handles tasks for the repositories of the Ionic Framework project.","https://github.com/ionic-team/ionic-issue-bot","2018/1/30 16:15:59","2018/10/24 15:20:45","{'checks': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'repository_projects': 'read', 'statuses': 'read'}","['check_run', 'check_suite', 'issues', 'issue_comment', 'label', 'project_card', 'pull_request', 'status']"
"44","48","guardrails","guardrailsio","31360611","Organization","GuardRails","![GuardRails](https://docs.guardrails.io/assets/images/social-card.jpg)
## What is GuardRails?
GuardRails provides **continuous security** feedback for modern development teams.
### What to expect?
GuardRails scans new code changes as they happen in your repositories. For pull requests, we will post comments whenever security issues are detected. For branches, you will be able to see reports in [your dashboard](https://dashboard.guardrails.io/login).
<img src=""https://gallery.mailchimp.com/6c07c586e98eabf488f8ee14f/images/ee5bf0d2-a37a-43c7-b4ed-57a1d4e2fa42.png"" alt=""Supported Languages"" height=""38""/>
We currently support **static code analysis** and **vulnerable dependencies analysis** for JavaScript, Python, Ruby, Solidity, Go, PHP, Elixir, C/C++ and Java. However, GuardRails can be used on all repositories to identify and prevent secrets leakage thanks to our **secrets detection** engines. We are working on adding support for C#/.NET next.
![GuardRails Dashboard](https://gallery.mailchimp.com/6c07c586e98eabf488f8ee14f/images/9a54898c-f0f6-41cb-ad20-1d6a8ad7c9a2.jpg)
### What else?
GuardRails works out of the box, _no configuration required_. However, if you want a custom experience, please refer to our documentation for the [configuration](https://www.guardrails.io/docs/en/configuration) options. For example, you can already **integrate GuardRails with Slack** to get the right notifications right where you are used to getting them.
![GuardRails + Slack](https://marketplace-screenshots.githubusercontent.com/2860/1d654680-512f-11e9-9791-794d77396fef?auto=webp&format=jpeg&width=670)
## Support
If you experience any difficulties or have any questions, you can reach out to us by [email](mailto:support@guardrails.io), on [Twitter](https://twitter.com/guardrailsio) or directly via [our support website](https://support.guardrails.io/).","https://www.guardrails.io","2017/9/27 10:36:01","2021/1/4 02:03:27","{'contents': 'read', 'emails': 'read', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write', 'vulnerability_alerts': 'read'}","['organization', 'pull_request', 'push', 'repository']"
"45","49","gcf-merge-on-green","dpebot","19979279","User","GCF Merge on Green","it merges PRs on green (when all of their tests and other required checks have passed).","https://github.com/googleapis/repo-automation-bots","2020/1/22 00:05:31","2020/1/29 00:23:31","{'administration': 'read', 'checks': 'write', 'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['pull_request']"
"46","50","p42-ai","p42ai","69107504","Organization","P42.ai","#### Write modern, clear, and concise code. For JavaScript and TypeScript.
P42 analyzes your GitHub repositories and provides suggestions. You can then use the [P42 Programming Assistant for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=p42ai.refactor) to review and apply the suggestions.
P42 needs the following permissions:
* To **analyze your JavaScript and Typescript code**, P42 needs **read-only access to code**.
* To **check your commits and pull requests**, P42 needs **read & write access to checks** and **read-only access to pull requests**.
You can choose which repositories you want to share with P42.
&nbsp;
&nbsp;
&nbsp;
![P42 Programming Assistant](https://p42.ai/image/illustration/robot_juggling.svg)","https://p42.ai","2020/10/2 09:10:00","2021/9/12 15:59:03","{'checks': 'write', 'contents': 'read', 'metadata': 'read', 'pull_requests': 'read'}","['check_run', 'check_suite', 'create', 'delete', 'public', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'push', 'repository']"
"47","51","toc-me","pholleran","4007128","User","toc-me","This app examines each push operation for markdown files formatted to use [markdown-toc](https://github.com/jonschlinkert/markdown-toc). When such files are found, toc-me regenerates a new ToC for the file and inserts it in the configured location.","https://github.com/pholleran/toc-me","2018/6/21 20:37:02","2018/6/26 17:08:46","{'checks': 'write', 'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'read'}","['issues', 'pull_request', 'push']"
"48","52","peril-staging","danger","17147106","Organization","Peril-Staging","The Orta hosted Peril, staging version, it's based on danger/peril master.
Warning: Only people who are inside the danger org can set up their projects once inside.
This version is what we use on the Artsy org, so it's reliable enough.","https://staging.peril.systems","2017/12/18 13:08:42","2018/9/8 16:45:41","{'checks': 'write', 'contents': 'write', 'deployments': 'read', 'issues': 'write', 'members': 'write', 'metadata': 'read', 'pull_requests': 'write', 'repository_projects': 'read', 'statuses': 'write'}","['check_run', 'check_suite', 'create', 'issues', 'issue_comment', 'label', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'push', 'release', 'repository', 'status']"
"49","53","prettifier","kevgo","268934","User","Prettifier","Prettifier keeps your repository content formatted using [https://prettier.io](Prettier). Standardized code formatting prevents pointless bikeshed debates and makes us feel more at home in each other's code. Pull requests no longer contain unnecessary whitespace changes. More info at [prettifier.io](https://www.prettifier.io).
## Direct fixes
Prettifier fixes formating issues directly:
<img src=""https://www.prettifier.io/features/format-via-commit.png"" width=""547"" height=""106"">
## Pull requests
If a direct fix isn't possible, Prettifier opens a pull request with the formatting fixes:
<img src=""https://www.prettifier.io/features/format-via-pull-request.png"" width=""576"" height=""440"">
","https://github.com/kevgo/prettifier","2018/11/26 17:42:20","2021/3/21 16:43:42","{'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['issue_comment', 'pull_request', 'push']"
"50","54","flaky-bot","dpebot","19979279","User","Flaky Bot","Listen on PubSub queue for broken builds, and open corresponding issues.","https://github.com/googleapis/repo-automation-bots","2019/12/18 20:46:44","2021/1/25 17:13:54","{'checks': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['pull_request']"
"51","55","size-plugin","kuldeepkeshwar","10448534","User","Size Plugin","A Github bot for size-plugin","https://github.com/kuldeepkeshwar/size-plugin-bot","2019/7/5 13:35:55","2019/7/9 17:25:48","{'administration': 'write', 'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['issues', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'push']"
"52","56","gcf-owl-bot","dpebot","19979279","User","GCF Owl Bot","Watches for changes to Google Cloud API protos, creates and post processes pull requests against client libraries.","https://github.com/googleapis/repo-automation-bots","2021/2/3 23:26:59","2021/2/3 23:28:37","{'checks': 'write', 'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'workflows': 'write'}","['pull_request', 'push']"
"53","57","not-a-robot","badboy","2129","User","not-a-robot","A merge bot for GitHub Pull Requests ","http://not-a-robot.herokuapp.com/","2017/2/5 12:15:28","2017/6/30 18:08:49","{'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['issue_comment', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'repository', 'status']"
"54","58","femtocleaner","JuliaComputing","10258468","Organization","femtocleaner","Cleans your julia projects by upgrading deprecated syntax, removing version compatibility workarounds and anything else that has a unique upgrade path.
DO NOT USE FOR PRIVATE REPOSITORIES.
Photo credit: <a href=""http://www.freepik.com/free-photos-vectors/business"">Business image created by Kjpargeter - Freepik.com</a>","https://github.com/JuliaComputing/FemtoCleaner.jl","2017/7/30 21:20:03","2017/10/27 14:55:30","{'checks': 'write', 'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['check_run', 'check_suite', 'commit_comment', 'issues', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'push', 'release']"
"55","60","backporting","tibdex","6574550","User","Backporting","This was the publicly hosted instance of the Backport GitHub App.
[Backport](https://github.com/tibdex/backport) is now a GitHub Action in the [Marketplace](https://github.com/marketplace/actions/backport).","https://github.com/tibdex/backport","2018/8/8 22:18:37","2019/11/17 19:37:33","{'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['pull_request']"
"56","61","sonatype-depshield","DepShield","39319176","Organization","Sonatype DepShield","Vulnerability Scanning for the Source","https://depshield.github.io","2018/6/20 22:30:15","2018/7/30 22:28:50","{'checks': 'write', 'contents': 'read', 'issues': 'write', 'metadata': 'read'}","['push']"
"57","62","failure-checker","dpebot","19979279","User","Failure Checker","Check for stalled releases, and other failures in client library automation and notify maintainers.","https://github.com/googleapis/repo-automation-bots","2019/11/23 00:06:32","2019/11/23 00:11:36","{'issues': 'write', 'metadata': 'read', 'single_file': 'read'}","[]"
"58","63","sourcery-ai","sourcery-ai","36609879","Organization","Sourcery AI","Sourcery is your team's refactoring AI that understands and improves code during pull requests reviews.
- Sourcery will refactor all incoming pull requests ensuring top quality is always maintained
","https://sourcery.ai","2019/12/6 13:02:12","2021/4/12 22:38:52","{'contents': 'write', 'emails': 'read', 'issues': 'read', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['issue_comment', 'member', 'organization', 'pull_request', 'push']"
"59","64","label-actions","dessant","7513068","User","Label Actions","⚠️ **This app is no longer maintained, please migrate to [Label Actions](https://github.com/dessant/label-actions).**
A GitHub App that performs actions when issues or pull requests are labeled or unlabeled.
## How It Works
The app performs certain actions when an issue or pull request is labeled or unlabeled. No action is taken by default and the app must be configured. The following actions are supported:
* Post a comment (`comment` option)
* Close (`close` option)
* Reopen (`open` option)
* Lock with an optional lock reason (`lock` and `lockReason` options)
* Unlock (`unlock` option)
## Usage
1. **[Install the GitHub App]()** for the intended repositories
2. Create `.github/label-actions.yml` based on the template below
3. Start labeling issues and pull requests
**If possible, install the app only for select repositories. Do not leave the `All repositories` option selected, unless you intend to use the app for all current and future repositories.**
#### Configuration
Create `.github/label-actions.yml` in the default branch to enable the app, or add it at the same file path to a repository named `.github`. Configure the app by editing the following template:
```yaml
# Configuration for Label Actions - https://github.com/dessant/label-actions-app
# Specify actions for issues and pull requests
actions:
# Actions taken when the `heated` label is added
heated:
# Post a comment
comment: >
The thread has been temporarily locked.
Please follow our community guidelines.
# Lock the thread
lock: true
# Set a lock reason, such as `off-topic`, `too heated`, `resolved` or `spam`
lockReason: ""too heated""
# Actions taken when the `heated` label is removed
-heated:
# Unlock the thread
unlock: true
# Optionally, specify configuration settings just for issues
issues:
actions:
feature:
# Post a comment, `{issue-author}` is an optional placeholder
comment: >
:wave: @{issue-author}, please use our idea board to request new features.
# Close the issue
close: true
-wontfix:
# Reopen the issue
open: true
# Optionally, specify configuration settings just for pull requests
pulls:
actions:
pizzazz:
comment: >
![](https://i.imgur.com/WuduJNk.jpg)
# Limit to only `issues` or `pulls`
# only: issues
# Repository to extend settings from
# _extends: repo
```
","https://github.com/dessant/label-actions-app","2019/1/23 11:59:29","2021/10/5 10:40:19","{'metadata': 'read', 'single_file': 'read'}","[]"
"60","65","allstar-app","ossf","67707773","Organization","Allstar App","Allstar allows you to specify and enforce security policies for your GitHub organization. See the repo documentation for usage.
Instance of Allstar run by OpenSSF","https://github.com/ossf/allstar","2021/6/8 16:10:42","2021/6/28 19:09:06","{'actions': 'read', 'administration': 'read', 'checks': 'write', 'contents': 'read', 'deployments': 'read', 'discussions': 'read', 'environments': 'read', 'issues': 'write', 'metadata': 'read', 'organization_packages': 'read', 'packages': 'read', 'pages': 'read', 'pull_requests': 'read', 'repository_hooks': 'read', 'repository_projects': 'read', 'secret_scanning_alerts': 'read', 'security_events': 'read', 'statuses': 'read', 'vulnerability_alerts': 'read'}","[]"
"61","66","stickler-ci","stickler-ci","16011037","User","Stickler CI","Align your team's code reviews with automatic style feedback, for all the languages you use, all in one place. Automatically fix style errors, and get inline comments when issues cannot be automatically fixed.
Configuration data is managed through your `.stickler.yml` file allowing you to keep your code style rules with your code.","https://stickler-ci.com","2018/7/28 02:13:46","2018/8/5 02:38:51","{'checks': 'write', 'contents': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['public', 'pull_request', 'repository']"
"62","67","required-files-bot","jpoehnelt","3392975","User","Required Files Bot","Github Bot to open issues for required files.
> **Note:** This bot is still **in development**.
> **Note:** This bot only works on public repositories in order to avoid requiring excessive permissions.
### Default Configuration
```yaml
files:
- LICENSE
branch: master
```
Override with your own `.github/required.yml`
### About
Built with [Probot](https://github.com/probot/probot).","https://medium.com/@jpoehnelt","2020/2/6 20:06:43","2020/4/23 00:38:05","{'issues': 'write', 'metadata': 'read', 'single_file': 'read'}","[]"
"63","68","firefoxci-taskcluster","mozilla-releng","19614164","Organization","firefoxci-taskcluster","Firefox CI Taskcluster","https://firefox-ci-tc.services.mozilla.com","2019/10/22 18:08:33","2019/11/12 17:52:39","{'administration': 'read', 'checks': 'write', 'contents': 'read', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['pull_request', 'push', 'release']"
"64","69","packit-as-a-service","packit","46870917","Organization","Packit-as-a-Service","[Packit](https://github.com/packit-service/packit) as a service.
You can find more info how to starting using Packit over here: [packit.dev/packit-as-a-service/](https://packit.dev/packit-as-a-service).","https://packit.dev/packit-as-a-service/","2019/4/16 15:27:36","2020/1/7 14:49:17","{'checks': 'write', 'contents': 'read', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['check_run', 'issue_comment', 'pull_request', 'push', 'release']"
"65","70","ansible-zuul","ansible-network","36541715","Organization","Ansible Zuul","GitHub app used by https://dashboard.zuul.ansible.com","https://dashboard.zuul.ansible.com","2019/3/27 14:45:29","2019/9/13 19:37:23","{'administration': 'read', 'checks': 'write', 'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['check_run', 'commit_comment', 'create', 'issues', 'issue_comment', 'label', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'push', 'release', 'status']"
"66","71","softwarefactory-project-zuul","softwarefactory-project","26543671","Organization","softwarefactory-project-zuul","The softwarefactory-project ZuulV3 based CI.","https://softwarefactory-project.io","2017/11/22 01:35:55","2021/7/8 14:19:38","{'administration': 'read', 'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['commit_comment', 'create', 'issues', 'issue_comment', 'label', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'push', 'release', 'status']"
"67","72","bors-voyager","carols10cents","193874","User","bors-voyager","Testing out bors-ng on crates.io","https://bors-voyager.herokuapp.com","2017/7/28 22:22:51","2017/7/28 22:22:51","{'checks': 'write', 'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['check_run', 'check_suite', 'issue_comment', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'repository', 'status']"
"68","73","probot-auto-merge","bobvanderlinden","6375609","User","probot-auto-merge","A Probot app that automatically merges pull requests once certain conditions are satisfied.
See https://github.com/bobvanderlinden/probot-auto-merge for more information.","https://github.com/bobvanderlinden/probot-auto-merge","2018/7/12 18:59:40","2019/5/2 13:40:58","{'administration': 'read', 'checks': 'write', 'contents': 'write', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'read'}","['check_run', 'check_suite', 'label', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'status']"
"69","74","chef-expeditor","chef","29740","Organization","Chef Expeditor","Expeditor is a release management utility built by Chef Software, Inc. to manage all the various software projects it maintains—open source or otherwise. It handles repetitive tasks like version bumping, CHANGELOG generation and release build triggering.
Please Note: This app will only work with Chef Software GitHub organizations. Do not install into the chef-boneyard organization, as that organization is used for acceptance/testing purposes. ","https://expeditor.chef.io","2019/4/1 17:36:28","2021/3/3 13:57:59","{'administration': 'write', 'checks': 'write', 'contents': 'write', 'deployments': 'write', 'issues': 'write', 'members': 'write', 'metadata': 'read', 'organization_administration': 'write', 'organization_hooks': 'write', 'organization_plan': 'read', 'organization_projects': 'admin', 'organization_user_blocking': 'write', 'pages': 'write', 'pull_requests': 'write', 'repository_hooks': 'write', 'repository_projects': 'admin', 'statuses': 'write', 'team_discussions': 'write', 'vulnerability_alerts': 'read', 'workflows': 'write'}","['check_run', 'check_suite', 'issues', 'pull_request', 'push', 'release', 'repository']"
"70","75","servarr","Servarr","57051827","Organization","Servarr","Bot to help keep various Sonarr forks up to date","https://githubbot.servarr.com","2020/7/30 04:58:56","2020/8/3 09:32:30","{'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['issue_comment', 'pull_request', 'push']"
"71","76","mergecat","soutaro","139089","User","MergeCat","MergeCat merges your Pull-Request !","https://www.mergecat.com","2017/7/21 10:59:34","2019/2/1 10:25:32","{'contents': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'read'}","['pull_request', 'pull_request_review', 'status']"
"72","77","patchback","pyba","47092190","Organization","Patchback","Patchback backports your PRs. It currently powers @aio-libs, @ansible, @ansible-collections, and @CherryPy.
author: [**@webknjaz**](https://github.com/sponsors/webknjaz)
src: https://github.com/sanitizers/patchback-github-app","https://github.com/apps/patchback","2018/11/28 16:43:36","2021/7/21 13:39:10","{'checks': 'write', 'contents': 'write', 'metadata': 'read', 'pull_requests': 'write', 'single_file': 'read', 'workflows': 'write'}","['pull_request']"
"73","78","blitzjs-bot","blitz-js","61243378","Organization","Blitzjs Bot","Delicious Automation :)","https://github.com/blitz-js/bot-github","2020/4/30 19:36:29","2020/5/15 03:21:06","{'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'repository_projects': 'write'}","['issues', 'issue_comment', 'project_card', 'pull_request']"
"74","79","npmbuildbot-nextcloud","nextcloud","19211038","Organization","npmbuildbot-nextcloud","A probot app that tries to compile npm assets and commit","https://github.com/skjnldsv/npmbuildbot","2019/4/12 11:50:39","2020/10/17 08:52:51","{'contents': 'write', 'issues': 'write', 'pull_requests': 'write'}","['issues', 'issue_comment', 'pull_request']"
"75","80","bulldozer-balena","balenaci","61781708","Organization","Bulldozer-Balena","Bulldozer Automerge Github App","https://bulldozer.product-os.io","2020/3/20 08:56:11","2020/5/20 21:07:32","{'administration': 'read', 'checks': 'read', 'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'read'}","['check_run', 'commit_comment', 'issue_comment', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'push', 'status']"
"76","81","lingohub","lingohub","1424397","Organization","LingoHub","LingoHub is a translation management software that helps teams localize software: Collaboratively, effectively, and more fun.
Customers such as Esports League, Universal, Rocket.Chat or Adidas Running use LingoHub to internationalize their apps, games or websites. LingoHub helps developers focus on their main work and eliminates the hassle of software translations.","https://lingohub.com","2020/8/19 13:48:41","2020/8/28 14:05:30","{'checks': 'write', 'contents': 'write', 'deployments': 'write', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'repository_hooks': 'write', 'statuses': 'write'}","[]"
"77","82","iptv-bot","freearhey","7253922","User","iptv-bot","","https://github.com/iptv-org","2021/5/26 15:17:23","2021/5/30 12:59:19","{'contents': 'write', 'metadata': 'read', 'pull_requests': 'write'}","[]"
"78","83","blathers-crl","otan-cockroach","57117177","Organization","blathers[crl]","Hoot! I should open a museum.
This is an automated bot for handling external contributions and some internal chores for cockroach. ","https://github.com/cockroachdb/cockroach","2020/4/3 20:07:35","2021/10/13 23:18:32","{'administration': 'read', 'checks': 'write', 'contents': 'write', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'organization_projects': 'write', 'pull_requests': 'write', 'repository_projects': 'write', 'statuses': 'write', 'team_discussions': 'read'}","['issues', 'issue_comment', 'project_card', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'status']"
"79","84","amaze-issue-automation","TeamAmaze","30984365","Organization","Amaze Issue Automation","Want to automate GitHub issue creation? Use this app and get away with the burden of implementing GitHub authentication APIs
Steps:
---
- Add this app to the repository and give it Issue read / write and metadata read permission.
- Generate the private key for your installation. Follow [this](https://docs.github.com/en/free-pro-team@latest/developers/apps/authenticating-with-github-apps) article for the same
- Deploy [this](https://github.com/TeamAmaze/amaze-github-automation) API function on your preferred hosting.","https://github.com/TeamAmaze/amaze-github-automation","2020/12/22 10:05:09","2020/12/26 13:27:43","{'issues': 'write', 'metadata': 'read'}","[]"
"80","85","dagsterbot","helloworld","3893054","User","DagsterBot","","https://docs.dagster.io","2021/3/5 03:26:23","2021/3/11 20:47:15","{'issues': 'write', 'metadata': 'read'}","[]"
"81","86","sentry-for-tribler","drew2a","13798583","User","Sentry-for-Tribler","This application has been created regarding https://develop.sentry.dev/integrations/github/
It allows linking [Sentry issues](https://sentry.tribler.org/) to [GithHub issues](https://github.com/Tribler/tribler/issues).","https://sentry.tribler.org","2020/11/4 13:31:04","2020/11/4 13:47:46","{'administration': 'read', 'contents': 'read', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'repository_hooks': 'write'}","[]"
"82","87","menbotics","frank-zsy","8512426","User","Menbotics","Menbotics is an open source project mentor to manage your project as you configured.","https://smee.io/xnijHeQikyGQmq9","2019/11/25 04:11:34","2019/12/18 07:13:44","{'actions': 'write', 'administration': 'read', 'checks': 'write', 'contents': 'write', 'deployments': 'read', 'issues': 'write', 'metadata': 'read', 'pages': 'read', 'pull_requests': 'write', 'repository_hooks': 'read'}","['check_run', 'check_suite', 'commit_comment', 'delete', 'fork', 'issues', 'issue_comment', 'label', 'public', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'push', 'release', 'repository', 'star', 'watch']"
"83","88","rootcause","bryntum","2638492","Organization","RootCause","With RootCause, you can record & replay user sessions to reproduce javascript errors in your website in no time.","https://app.therootcause.io/","2018/2/10 17:33:14","2020/2/20 21:16:19","{'issues': 'write', 'metadata': 'read'}","[]"
"84","89","servarr-sentry","Servarr","57051827","Organization","Servarr Sentry","","https://sentry.servarr.com","2020/4/26 19:14:07","2020/4/27 09:34:52","{'administration': 'read', 'contents': 'read', 'emails': 'read', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'organization_administration': 'read', 'organization_projects': 'read', 'pull_requests': 'write', 'repository_hooks': 'write'}","['pull_request', 'push']"
"85","90","adsmerger","kburtram","599935","User","adsmerger","","https://github.com/Microsoft/azuredatastudio","2019/2/28 23:43:16","2020/9/15 01:53:49","{'administration': 'write', 'contents': 'write', 'deployments': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['issues', 'issue_comment']"
"86","91","bridgecrew-develop","bridgecrewio","48174253","Organization","Bridgecrew-develop","ONLY FOR DEVELOP!!!
Find & fix security and compliance issues in Terraform and AWS CloudFormation
","http://bridgecrew-app-619572639823-mike3.s3-website-us-west-2.amazonaws.com","2020/2/9 14:55:37","2021/10/16 01:09:42","{'checks': 'write', 'contents': 'write', 'emails': 'read', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write', 'vulnerability_alerts': 'read'}","['commit_comment', 'create', 'issues', 'public', 'pull_request', 'pull_request_review_comment', 'push', 'repository']"
"87","92","incident-io","incident-io","76436871","Organization","incident-io","The [incident.io](https://incident.io) GitHub integration for following up on actions from incidents.","https://incident.io","2021/3/19 14:19:05","2021/3/19 14:36:08","{'issues': 'write', 'members': 'read', 'metadata': 'read'}","[]"
"88","93","gutenberg-plugin-upgrade-bot","chad1008","13856531","User","Gutenberg Plugin Upgrade Bot™","","https://github.com/Automattic/wp-calypso","2021/10/8 15:05:03","2021/10/11 18:15:34","{'issues': 'write', 'metadata': 'read'}","[]"
"89","94","reunion-maestro","microsoft","6154722","Organization","Reunion-Maestro","Github app for maestro","https://reunion-maestro-prod.westus2.cloudapp.azure.com/","2021/3/22 22:44:15","2021/12/10 22:29:15","{'actions': 'read', 'administration': 'read', 'checks': 'write', 'contents': 'write', 'deployments': 'read', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'repository_hooks': 'write', 'statuses': 'read'}","['pull_request', 'pull_request_review', 'pull_request_review_comment', 'push']"
"90","95","logrocket","LogRocket","19847951","Organization","LogRocket","This integration allows LogRocket to create issues in selected GitHub repositories. ","https://logrocket.com","2016/11/7 02:43:36","2017/3/30 19:45:00","{'issues': 'write', 'metadata': 'read'}","['issues', 'issue_comment']"
"91","96","codefactor-io","codefactor-io","11671095","Organization","codefactor.io","CodeFactor.io seamlessly integrates with GitHub, instantly performs Code Review with every GitHub Commit or PR. Zero setup time. Get actionable feedback within seconds for any branch. Customize rules and ignore irrelevant issues.","https://www.codefactor.io","2019/2/19 08:55:48","2019/5/27 05:35:54","{'administration': 'read', 'checks': 'write', 'contents': 'write', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'repository_hooks': 'write', 'statuses': 'write'}","['member', 'membership', 'organization', 'pull_request', 'push', 'repository', 'team', 'team_add']"
"92","97","algorithms-keeper","dhruvmanila","67177269","User","algorithms-keeper","# algorithms-keeper
[![GitHub Workflow Status](https://img.shields.io/github/workflow/status/dhruvmanila/algorithms-keeper/CI?label=CI&logo=github&style=flat-square)](https://github.com/dhruvmanila/algorithms-keeper/actions) [![Codecov](https://img.shields.io/codecov/c/gh/dhruvmanila/algorithms-keeper?label=codecov&logo=codecov&style=flat-square)](https://codecov.io/gh/dhruvmanila/algorithms-keeper) [![code style: black](https://img.shields.io/static/v1?label=code%20style&message=black&color=black&style=flat-square)](https://github.com/psf/black)
A bot for [TheAlgorithms/Python](https://www.github.com/TheAlgorithms/Python) repository. This bot is based on [this tutorial](https://github-app-tutorial.readthedocs.io/en/latest/index.html) and also inspired by the ones working for the [CPython](https://github.com/python/cpython) repository which are [miss-islington](https://github.com/python/miss-islington), [bedevere](https://github.com/python/bedevere) and [the-knights-who-say-ni](https://github.com/python/the-knights-who-say-ni). This bot is basically a GitHub app which can be installed in any repository using [this link](https://github.com/apps/algorithms-keeper).
***NOTE: This bot is highly configured for [TheAlgorithms/Python](https://www.github.com/TheAlgorithms/Python) repository. DO NOT INSTALL the bot without reading what it actually does.***
## What the bot does:
### Greet the user for installing the app
Open an issue with the message greeting the user who either installed the app or added a new repository to the installed app and then close the issue.
### Add or remove label(s) to pull requests
- To indicate that some of the tests are failing for this pull request if it is not present and remove it when all the tests are passing. It does nothing if the tests are already passing. ***NOTE: This check will be skipped if the pull request is in draft mode.***
- To indicate that the pull request is ready to be reviewed by a maintainer which means all the checks are passing and all the requirements have been satisfied.
- To indicate the user that a maintainer has requested some changes to their submission. The bot will remove the label once the pull request is approved.
### Close invalid pull requests
A pull request is considered invalid if:
- It doesn't contain any description.
- The user has not ticked any of the checkboxes in the provided pull request template.
- The file extension is invalid. For now only PRs with extensionless files are closed.
***NOTE: These checks will be skipped for any member or owner of the organization and also for the pull request which is in draft mode.***
### Close additional pull requests by user
A user will be allowed a fix number of pull requests at a time which will be indicated by the `MAX_PR_BY_USER` constant. This is done so as to avoid spam pull requests. This can be disabled by updating the constant value to 0: `MAX_PR_BY_USER = 0`.
***NOTE: These checks will be skipped for any member or owner of the organization and also for the pull request which is in draft mode.***
### Check all Python files in a pull request
All the Python files will be checked for tests [`doctest`/`unittest`/`pytest`], type hints and descriptive class/function/parameter names. Labels will be added and/or removed according to the latest commit in a pull request. A report will be created and commented by the bot if there are any errors found, but ***only*** when a pull request is ***opened*** or is made ***ready for review*** and not on the subsequent commits.
***NOTE: These checks will be skipped if the pull request is in draft mode and if the pull request is invalid.***
## Logging
There are three loggers out of which one is the main `logger` for the bot that is being used to log certain events and exceptions. The other two loggers are: `aiohttp.access` from `aiohttp.log.access_logger`, used to log `POST` requests made by GitHub for delivering the payload and `api`, used to log all the API calls made to GitHub. The logs can be viewed best using the following command ([_requires Heroku CLI_](https://devcenter.heroku.com/articles/heroku-cli#download-and-install)):
```commandline
heroku logs -a algorithms-keeper -d web -t
```
","https://github.com/dhruvmanila/algorithms-keeper","2020/10/25 08:57:23","2020/11/22 06:44:16","{'actions': 'write', 'checks': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['check_run', 'issues', 'issue_comment', 'pull_request', 'pull_request_review', 'workflow_run']"
"93","98","gopherci","bradleyfalzon","1834577","User","GopherCI","GopherCI is a continuous integration tool to check the Go repositories for breaking changes and other static analysis tools.","https://gopherci.io","2016/12/20 10:06:13","2017/4/12 03:06:49","{'contents': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['pull_request', 'push', 'repository']"
"94","100","stale","probot","26350515","Organization","Stale","> a GitHub Integration built with [Probot](https://github.com/probot/probot) that closes abandoned issues after a period of inactivity.
[![](https://cloud.githubusercontent.com/assets/173/23858697/4885f0d6-07cf-11e7-96ed-716948027bbc.png)](https://github.com/probot/demo/issues/2)
After installing the integration, create `.github/stale.yml` in the default branch to enable it:
```yml
# Number of days of inactivity before an issue becomes stale
daysUntilStale: 60
# Number of days of inactivity before a stale issue is closed
daysUntilClose: 7
# Issues with these labels will never be considered stale
exemptLabels:
- pinned
- security
# Label to use when marking an issue as stale
staleLabel: wontfix
# Comment to post when marking an issue as stale. Set to `false` to disable
markComment: >
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Thank you
for your contributions.
# Comment to post when closing a stale issue. Set to `false` to disable
closeComment: false
```
","https://probot.github.io/apps/stale/","2017/3/13 14:06:37","2018/3/22 04:00:33","{'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'single_file': 'read'}","['issues', 'issue_comment', 'pull_request', 'pull_request_review', 'pull_request_review_comment']"
"95","101","codecov-io","xaxadmin","18427388","User","Codecov.io","Codecov provides highly integrated tools to group, merge, archive and compare coverage reports. Whether your team is comparing changes in a pull request or reviewing a single commit, Codecov will improve the code review workflow and quality.","https://codecov.io/","2017/7/2 04:31:02","2019/9/26 06:45:33","{'administration': 'write', 'contents': 'write', 'deployments': 'write', 'issues': 'write', 'members': 'write', 'metadata': 'read', 'organization_projects': 'write', 'pages': 'write', 'pull_requests': 'write', 'repository_projects': 'write', 'statuses': 'write', 'team_discussions': 'read'}","['commit_comment', 'create', 'delete', 'deployment', 'deployment_status', 'fork', 'gollum', 'issues', 'issue_comment', 'label', 'member', 'membership', 'milestone', 'organization', 'page_build', 'project', 'project_card', 'project_column', 'public', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'push', 'release', 'repository', 'status', 'team', 'team_add', 'watch']"
"96","102","codecov","codecov","8226205","Organization","Codecov","Codecov provides highly integrated tools to group, merge, archive and compare coverage reports. Whether your team is comparing changes in a pull request or reviewing a single commit, Codecov will improve the code review workflow and quality.
## Code coverage done right.®
1. Upload coverage reports from your CI builds.
2. Codecov merges all builds and languages into one beautiful coherent report.
3. Get commit statuses, pull request comments and coverage overlay via our browser extension.
When Codecov merges your uploads it keeps track of the CI provider (inc. build details) and user specified context, e.g. `#unittest` ~ `#smoketest` or `#oldcode` ~ `#newcode`. You can track the `#unittest` coverage independently of other groups. [Learn more here](
http://docs.codecov.io/docs/flags)
Through **Codecov's Browser Extension** reports overlay directly in GitHub UI to assist in code review. [Watch here](https://docs.codecov.io/docs/browser-extension)
*Highly detailed* **pull request comments** and *customizable* **commit statuses** will improve your team's workflow and code coverage incrementally.
**File backed configuration** all through the `codecov.yml`.
## FAQ
- Do you **merge multiple uploads** to the same commit? **Yes**
- Do you **support multiple languages** in the same project? **Yes**
- Can you **group coverage reports** by project and/or test type? **Yes**
- How does **pricing** work? Only paid users can view reports and post statuses/comments. ","https://codecov.io","2016/9/25 14:18:27","2020/8/27 18:10:18","{'administration': 'read', 'checks': 'write', 'contents': 'read', 'issues': 'read', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['check_run', 'check_suite', 'create', 'delete', 'fork', 'member', 'membership', 'organization', 'public', 'pull_request', 'push', 'release', 'repository', 'status', 'team_add']"
"97","103","google-cla","google","1342004","Organization","Google CLA","This is Google's CLA validation tool.
See https://cla.developers.google.com/ for more information.","https://cla.developers.google.com/","2019/9/26 21:40:56","2020/7/16 01:09:01","{'checks': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['issue_comment', 'pull_request']"
"98","104","lgtm-com","Semmle","1101495","Organization","LGTM.com","![](https://lgtm.com/static/images/github-app/github-app-header.svg)
## Continuous security analysis
LGTM is a code analysis platform for identifying vulnerabilities early and preventing them from reaching production.
LGTM automatically runs over 1600 standard analyses contributed to by top researchers from the [Semmle Security Research Team](https://semmle.com/security) and our growing customer community – including Microsoft, Google, Uber and Mozilla.
Quickly refine and run custom queries to find variants of known issues and prevent them from being re-introduced into your codebase.
### Automatic code review for pull requests
LGTM only notifies you of new (and fixed!) alerts. This way, it's low-noise, but still allows you to detect critical problems early and fix them before they’re merged!
![](https://lgtm.com/static/images/github-app/github-app-checks.png)
### Prioritized alert overview
View the alerts for the latest commit of your project, smartly prioritized based on the alert severity, your project history, and the behaviour of developers across over 130,000 repos. Extensive filters also allow you to focus on the results that are most important to you.
![](https://lgtm.com/static/images/github-app/github-app-alerts.png)","https://lgtm.com/","2018/9/10 15:15:00","2019/8/26 15:25:07","{'checks': 'write', 'emails': 'read', 'metadata': 'read', 'pull_requests': 'write'}","['pull_request']"
"99","105","netlify","netlify","7892489","Organization","Netlify","Publish incredibly high performance websites and applications right from GitHub. The Netlify platform connects your repositories to an all-in-one workflow for global CDN deployment, continuous integration, and automatic (and free) HTTPS. Each time you commit changes, Netlify builds your site, prerenders markup, and optimizes assets on dedicated build infrastructure. Easily create an entirely automated workflow around any site generator such as Jekyll, Hugo, or Gatsby.
## Features
### Push your site live, directly from GitHub
Deploy your site to an ultra-redundant global CDN that’s purpose built for serving pages and assets quickly and consistently.
### Automate deployment
Netlify’s built-in Continuous Deployment automatically runs your build commands and deploys the result whenever you push to your Git repository.
### Add a custom domain
Purchase domains and manage DNS zones and records right inside of Netlify.
### HTTPS is automatic
Your site will automatically be secured with a free TLS certificate from Let’s Encrypt.
### Deploy Previews
Netlify’s Deploy Previews streamlined your workflow by giving you a unique, permanent URL to check what your changes will be like in production whenever you submit a pull request.
### And a lot more!
Netlify includes solutions for forms, identity, and even custom functions powered by AWS Lambda. And all this functionality can be configured directly in your repo.
","https://www.netlify.com","2018/6/12 15:16:51","2021/2/23 21:25:42","{'checks': 'write', 'contents': 'read', 'emails': 'read', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['create', 'delete', 'issue_comment', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'push']"
"100","106","no-response","probot","26350515","Organization","No Response","closes issues where the author hasn't responded to a request for more information","https://github.com/probot/no-response","2017/10/20 17:41:39","2017/10/20 17:49:07","{'issues': 'write', 'metadata': 'read', 'single_file': 'read'}","['issues', 'issue_comment']"
"101","108","sonarcloud","sonarcloud","39168408","User","SonarCloud","[SonarCloud](https://sonarcloud.io) is the leading online service to catch Security Vulnerabilities, Bugs, and Code Smells in your pull requests, branches and throughout your repository, with more than 1 billion lines of code analyzed every week.
SonarCloud integrates seamlessly into your GitHub workflow, and provides clear guidance for resolving any Code Quality and Code Security issues detected. We empower developers and development teams of all sizes to write cleaner and safer code, across 24 programming languages (including Java, JavaScript, TypeScript, C#, Python, C++ and many more). Many popular languages can be analyzed automatically; no configuration required!
With [Sonarcloud](https://sonarcloud.io/github), you get:
- Fast, precise feedback on your code
- Automatic analysis of pull requests and branches with results reported inline
- Quality Gate (added as a GitHub check) acting at two different levels - first, preventing you from merging pull requests that contain issues - and later, helping you to release only clean, safe code
A [GitHub Action](https://github.com/marketplace/actions/sonarcloud-scan) is available in the marketplace to make it easy for you (for projects where automatic analysis isn't available). SonarCloud also integrates smoothly with Jenkins, CircleCI, TravisCI, CirrusCI and many other tools.
No signup is required. Simply log in via GitHub and get your first code analysis report in minutes. Our service is entirely [free for open-source projects](https://sonarcloud.io/pricing), with paid plans for private projects starting at 10€ per month (Free 14-day trial).
","https://sonarcloud.io","2018/5/22 07:36:37","2021/6/7 12:38:15","{'checks': 'write', 'contents': 'read', 'emails': 'read', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['organization', 'pull_request', 'push', 'repository']"
"102","109","welcome","probot","26350515","Organization","Welcome","
> a GitHub App built with [probot](https://github.com/probot/probot) that welcomes new users based off maintainer defined comments that should be located in a `.github/config.yml`
The 3 plugins it combines with are [new-issue-welcome]
### New Issue Welcome:
[new-issue-welcome](https://github.com/behaviorbot/new-issue-welcome)
<img width=""801"" alt=""screen shot 2017-07-17 at 1 31 50 pm"" src=""https://user-images.githubusercontent.com/13410355/28288547-5f83aa8e-6af4-11e7-9692-eb41d42431e2.png"">
### New PR Welcome:
[new-pr-welcome](https://github.com/behaviorbot/new-pr-welcome)
<img width=""802"" alt=""screen shot 2017-07-07 at 10 40 26 am"" src=""https://user-images.githubusercontent.com/13410355/28288851-679f582a-6af5-11e7-8dd8-b85b6c33e16b.png"">
and [first-pr-merge](https://github.com/behaviorbot/new-issue-welcome)
<img width=""807"" alt=""screen shot 2017-07-17 at 1 58 37 pm"" src=""https://user-images.githubusercontent.com/13410355/28289605-1ab81a76-6af8-11e7-8f78-6a1b3948df36.png"">
## Usage
1. Install the bot on the intended repositories. The plugin requires the following **Permissions and Events**:
- Pull requests: **Read & Write**
- Issues: **Read & Write**
2. Create a `config.yml` file to check for content of the comments:
``` yaml
# Configuration for welcome - https://github.com/behaviorbot/welcome
# Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
# Comment to be posted to on first time issues
newIssueWelcomeComment: >
Thanks for opening your first issue here! Be sure to follow the issue template!
# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
# Comment to be posted to on PRs from first time contributors in your repository
newPRWelcomeComment: >
Thanks for opening this pull request! Please check out our contributing guidelines.
# Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
# Comment to be posted to on pull requests merged by a first time user
firstPRMergeComment: >
Congrats on merging your first pull request! We here at behaviorbot are proud of you!
# It is recommend to include as many gifs and emojis as possible
```
You can opt out of having the bot comment on first time pull requests, pull request merges, or new issues by not filling in a value for each app's respective field.","https://probot.github.io/apps/welcome/","2017/7/31 21:21:17","2017/9/28 16:06:25","{'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['issues', 'pull_request']"
"103","110","microsoft-cla","microsoft","6154722","Organization","Microsoft CLA","Microsoft's Contributor License Agreement (CLA) helps ensure that the community is free to use your contributions.","https://cla.opensource.microsoft.com","2020/5/26 22:46:28","2020/6/1 23:18:43","{'contents': 'read', 'emails': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","[]"
"104","111","codesandbox","codesandbox","32880324","Organization","CodeSandbox","## CI Built for Maintainers
Test pull requests without publishing to npm or cloning and installing locally.
### Here's how it works:
* CodeSandbox CI builds a version of your library for every PR.
* Builds get posted to our registry for testing in CodeSandbox or locally⁠.
* Bug reports with reproducible sandboxes are automatically created using the new PR build to review online.
For more information, see our [documentation](https://codesandbox.io/docs/ci).
![CodeSandbox CI bot](https://uploads.codesandbox.io/uploads/user/e4e9e8d4-095e-446c-8ad1-4e13fb5aecfb/Ceip-csbCIBotComment.png)","https://codesandbox.io","2019/8/13 19:47:41","2020/2/21 12:30:53","{'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['pull_request']"
"105","112","changeset-bot","changesets","51163350","Organization","changeset-bot","This bot will comment on PRs saying that either a user might need to add a changeset(note that PRs changing things like documentation generally don't need a changeset)or say that the PR is good and already has a changeset.
<img width=""1552"" alt=""screenshot of changeset bot message from https://github.com/mitchellhamilton/manypkg/pull/18 before a changeset was added"" src=""https://user-images.githubusercontent.com/11481355/66183943-dc418680-e6bd-11e9-998d-e43f90a974bd.png"">
<img width=""1552"" alt=""screenshot of the changeset bot message from https://github.com/mitchellhamilton/manypkg/pull/18 showing the changeset good to go message"" src=""https://user-images.githubusercontent.com/11481355/66184229-cf716280-e6be-11e9-950e-0f64a31dbf15.png"">
Sometimes, a contributor won't add a changeset to a PR but you might want to merge in the PR without having to wait on them to add it. To address this, this bot adds a link with the filename pre-filled to add a changeset so all you have to do is write the changeset and click commit.
<img width=""1552"" alt=""screenshot of the changeset bot message from https://github.com/mitchellhamilton/manypkg/pull/18 focused on the create a changeset link"" src=""https://user-images.githubusercontent.com/11481355/66184052-3a6e6980-e6be-11e9-8e62-8fd9d49af587.png"">
<img width=""1552"" alt=""screenshot of creating a changeset directly on GitHub"" src=""https://user-images.githubusercontent.com/11481355/66184086-5bcf5580-e6be-11e9-8227-c1ed6d96b5d2.png"">
<img width=""1552"" alt=""screenshot of the GitHub file creation page focusing on the commit button"" src=""https://user-images.githubusercontent.com/11481355/66184181-a94bc280-e6be-11e9-85fc-32edcd5b05ce.png"">
<img width=""1552"" alt=""screenshot of the changeset bot message from https://github.com/mitchellhamilton/manypkg/pull/18 showing the changeset good to go message"" src=""https://user-images.githubusercontent.com/11481355/66184229-cf716280-e6be-11e9-950e-0f64a31dbf15.png"">
When writing the changeset, it should look something like this with the packages that are being released in the YAML front matter with associated semver bump types and the summary of the changes in markdown.
```markdown
---
'@changesets/cli': major
'@changesets/read': minor
---
A very helpful description of the changes
```","https://github.com/changesets/changesets","2019/4/9 00:12:46","2019/10/4 05:53:40","{'contents': 'read', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['issues', 'pull_request']"
"106","113","linux-foundation-easycla","LF-Engineering","38015056","Organization","Linux Foundation: EasyCLA","The Contributor License Agreement (CLA) service of the Linux Foundation lets project contributors read, sign, and submit license agreements easily.","https://www.linuxfoundation.org/","2018/9/21 18:36:19","2020/11/7 20:38:10","{'administration': 'write', 'emails': 'read', 'issues': 'read', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'repository_hooks': 'write', 'statuses': 'write'}","['issue_comment', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'repository', 'status']"
"107","114","issue-label-bot","machine-learning-apps","49846054","Organization","Issue-Label Bot","https://github.com/marketplace/issue-label-bot
Issue Label Bot automatically labels issues as either a feature request, bug or question, using machine learning. You can alias these labels so that the labels are personalized for your repo (for example if you prefer enhancement vs. feature_request). This app will only make predictions on public repositories.
Customize the naming of labels:
To alias the labels bug, label, and feature_request, place a yaml file with this name and path in your repo: /.github/issue_label_bot.yaml See this example yaml file: https://github.com/machine-learning-apps/Issue-Label-Bot/blob/master/.github/issue_label_bot.yaml If the yaml fails to parse or an incorrect schema is used, the app will revert back to default label names.
Additional routes for existing users:
- See a sample of users with an active installation: https://mlbot.net/users
- See all repos w/installations for a specific user: https://mlbot.net/repos/{username}
- See the last 50 predictions for a specific repo: https://mlbot.net/data/{username}/{repo}
The code for this app is also open sourced under an MIT license. You can see the documentation, code, and example predictions on this page: https://mlbot.net/
If you have any suggestions, feature requests or just want to get in touch please open an issue: https://github.com/machine-learning-apps/Issue-Label-Bot/issues","https://github.com/marketplace/issue-label-bot","2019/3/16 03:44:52","2020/1/18 02:19:17","{'contents': 'read', 'issues': 'write', 'metadata': 'read'}","['issues', 'issue_comment']"
"108","115","request-info","probot","26350515","Organization","Request Info","# request-info
> a GitHub App built with [probot](https://github.com/probot/probot) that requests more info from newly opened Pull Requests and Issues that contain either default titles or whose description is left blank. It does so by taking data from a `.github/config.yml`.
<img width=""1041"" alt=""screen shot 2017-07-07 at 3 32 01 pm"" src=""https://user-images.githubusercontent.com/13410355/28132821-d37bf2a8-66f2-11e7-9e7b-5930ba65d67a.png"">
## Usage
1. Install the bot on the intended repositories. The plugin requires the following **Permissions and Events**:
- Pull requests: **Read & Write**
- [x] check the box for **Pull Request** events
- Issues: **Read & Write**
- [x] check the box for **Issue** events
2. Add a `.github/config.yml` file that contains the following:
```yml
# Configuration for request-info - https://github.com/behaviorbot/request-info
# *Required* Comment to reply with
requestInfoReplyComment: >
We would appreciate it if you could provide us with more info about this issue/pr!
# *OPTIONAL* default titles to check against for lack of descriptiveness
# MUST BE ALL LOWERCASE
requestInfoDefaultTitles:
- update readme.md
- updates
# *OPTIONAL* Label to be added to Issues and Pull Requests with insufficient information given
requestInfoLabelToAdd: needs-more-info
```","https://probot.github.io/apps/request-info/","2017/8/4 18:00:53","2017/9/28 16:06:55","{'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'single_file': 'read'}","['issues', 'pull_request']"
"109","116","gitcoinbot","owocki","513929","User","gitcoinbot","Gitcoinbot is a bot that allows you to interact with gitcoin via the github comments.","https://github.com/gitcoinco/web/tree/master/app/gitcoinbot","2017/12/27 18:23:26","2018/3/12 16:34:13","{'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['issue_comment', 'pull_request_review_comment']"
"110","117","issuehunt-app","BoostIO","13612118","Organization","Issuehunt app","Issue-based bounty platform for open source projects.","https://issuehunt.io","2019/5/1 06:14:59","2020/10/1 06:48:40","{'administration': 'read', 'contents': 'read', 'emails': 'read', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'organization_user_blocking': 'read', 'pull_requests': 'write', 'repository_hooks': 'write'}","['issues', 'issue_comment', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'repository', 'watch']"
"111","118","support","dessant","7513068","User","Support","⚠️ **This app is no longer maintained, please migrate to [Support Requests](https://github.com/dessant/support-requests).**
A GitHub App that comments on and closes issues labeled as support requests.
![](https://raw.githubusercontent.com/dessant/support-requests-app/master/assets/screenshot.png)
## Usage
1. **[Install the GitHub App]()** for the intended repositories
2. Create `.github/support.yml` based on the template below
3. Start labeling issues as support requests
**If possible, install the app only for select repositories. Do not leave the `All repositories` option selected, unless you intend to use the app for all current and future repositories.**
#### Configuration
Create `.github/support.yml` in the default branch to enable the app, or add it at the same file path to a repository named `.github`. The file can be empty, or it can override any of these default settings:
```yaml
# Configuration for Support Requests - https://github.com/dessant/support-requests-app
# Label used to mark issues as support requests
supportLabel: support
# Comment to post on issues marked as support requests, `{issue-author}` is an
# optional placeholder. Set to `false` to disable
supportComment: >
:wave: @{issue-author}, we use the issue tracker exclusively for bug reports
and feature requests. However, this issue appears to be a support request.
Please use our support channels to get help with the project.
# Close issues marked as support requests
close: true
# Lock issues marked as support requests
lock: false
# Assign `off-topic` as the reason for locking. Set to `false` to disable
setLockReason: true
# Repository to extend settings from
# _extends: repo
```
","https://github.com/dessant/support-requests-app","2017/11/2 05:13:59","2021/10/5 10:45:24","{'metadata': 'read', 'single_file': 'read'}","[]"
"112","119","close-issue-app","helloqiu","8971659","User","close-issue-app","A bot which helps you to close issues that don't include some specific contents.
See how to use it in https://github.com/offu/close-issue-app.","https://github.com/offu/close-issue-app","2018/5/28 06:11:31","2018/6/21 13:08:51","{'issues': 'write', 'metadata': 'read', 'repository_hooks': 'write'}","['issues']"
"113","121","codeclimate","codeclimate","789641","Organization","CodeClimate","Code Climate Github App provides line-by-line test coverage reports, proprietary 10-point technical debt assessments, and style checks for over 10 languages in every pull request. This tool will streamline your code review process, helping your team write maintainable and well-tested code. ","https://codeclimate.com/","2018/2/23 05:30:13","2018/5/11 16:02:31","{'contents': 'read', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","[]"
"114","124","weblate","WeblateOrg","18286565","Organization","Weblate","Weblate is a web-based continuous localization system.
","https://weblate.org/","2017/1/3 16:00:06","2019/6/16 04:33:41","{'contents': 'write', 'metadata': 'read'}","['push', 'repository']"
"115","125","cla-checker-service","elastic","6764390","Organization","CLA Checker Service","Integration with Docusign to collect and check signed [Contributor Agreements](https://www.elastic.co/contributor-agreement). This will let external contributors submit PRs to our codebase. ","https://clachecker.ea-web.elastic.dev/","2019/7/8 13:13:56","2020/2/20 06:21:23","{'contents': 'read', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'repository_hooks': 'write', 'statuses': 'write'}","['commit_comment', 'issue_comment', 'pull_request', 'pull_request_review', 'pull_request_review_comment']"
"116","126","cypress","cypress-io","8908513","Organization","Cypress","Access Cypress Dashboard results in your GitHub pull requests.
## Status checks
Cypress Dashboard will submit status checks for your cypress test runs. Mark
these status checks as required to ensure your Cypress tests pass before
merging!
## PR comments
Cypress Dashboard will publish comments with run statistics, test failures,
and related screenshots. It includes deep links to the relevant views in
Cypress Dashboard so you can quickly dig into test failures.","https://dashboard.cypress.io/","2018/2/14 04:54:57","2019/7/1 20:11:15","{'checks': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['pull_request', 'status']"
"117","127","cloudflare-pages","cloudflare","314135","Organization","Cloudflare Pages","","https://pages.cloudflare.com/","2020/10/19 20:23:00","2021/1/12 18:19:30","{'checks': 'write', 'contents': 'read', 'deployments': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['pull_request', 'push']"
"118","128","gitpod-io","gitpod-io","37021919","Organization","gitpod.io","Always ready to code - spin up fresh, automated dev environments for each task, in the cloud, in seconds.
![Screenshot](https://user-images.githubusercontent.com/372735/113861964-1c4c6280-97a8-11eb-9471-9e481a224f4a.png)
## How it works
Gitpod is an open-source Kubernetes application for automated and ready-to-code development environments that blends in your existing workflow. It enables you to describe your dev environment as code and start instant and fresh development environments for each new task directly from your browser.
It can be started on any GitHub URL by prefixing it with `gitpod.io#`.
Gitpod Bot does two things:
1. generate Gitpod links for pull requests and add them to the description,
2. prebuild workspaces for branches and pull requests.
## Installation
To install the app, make sure you are [logged in to Gitpod](https://gitpod.io/workspaces) beforehand.
After installing the app, configure it using the `.gitpod.yml` in the default branch:
```yml
github:
prebuilds:
# enable for the master/default branch (defaults to true)
master: true
# enable for all branches in this repo (defaults to false)
branches: true
# enable for pull requests coming from this repo (defaults to true)
pullRequests: true
# enable for pull requests coming from forks (defaults to false)
pullRequestsFromForks: true
# add a ""Review in Gitpod"" button as a comment to pull requests (defaults to true)
addComment: true
# add a ""Review in Gitpod"" button to pull requests (defaults to false)
addBadge: false
# add a label once the prebuild is ready to pull requests (defaults to false)
addLabel: prebuilt-in-gitpod
```
## More information
You can find more information at https://docs.gitpod.io","https://www.gitpod.io","2019/1/10 12:40:42","2021/7/26 13:16:11","{'contents': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['pull_request', 'push']"
"119","129","auto-comment","boyney123","3268013","User","auto-comment","Configure & automatically comment on issues and pull requests","https://github.com/apps/auto-comment","2018/7/5 07:35:32","2018/7/5 16:44:31","{'administration': 'read', 'contents': 'read', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'single_file': 'read'}","['issues', 'issue_comment', 'pull_request', 'pull_request_review', 'pull_request_review_comment']"
"120","132","scala-steward","scala-steward-org","45183761","Organization","Scala Steward","","https://scala-steward.org","2019/3/19 19:26:37","2020/11/30 13:39:44","{'metadata': 'read', 'pull_requests': 'write'}","[]"
"121","133","dotnet-issue-labeler","maryamariyan","5897654","User","dotnet-issue-labeler","Issue labeler for repositories under dotnet organization on GitHub.","https://dispatcher-app.azurewebsites.net/","2020/11/24 22:27:09","2021/10/14 05:32:42","{'issues': 'write', 'metadata': 'read', 'pull_requests': 'write'}","['issues', 'pull_request']"
"122","134","boring-cyborg","kaxil","8811558","User","boring-cyborg","A Github bot to automatically label PRs, issues and perform all the boring operations that you don't want to do.
![Using Boring Cyborg Probot to add new labels](https://raw.githubusercontent.com/kaxil/boring-cyborg/master/assets/usage-screenshot-1.png)
![Congratulate user on first merged PR](https://raw.githubusercontent.com/kaxil/boring-cyborg/master/assets/usage-first-merged-pr.gif)
## Features
* Add labels based on the path of the file that are modified in the PR.
* Welcome new users to your project when they open their first Issue/PR or first merged PR by an
automated comment.
* Insert Issue (Jira/Github etc) link in PR description based on the Issue ID in PR title.
* Verifies if commits/PR titles match the regular expression specified
* Check if a branch is up to date with the master when specific files are modified in the PR. This is helpful when you desire the changes to be applied sequentially, for example, alembic migrations.
## Usage
1. **[Configure the Github App](https://github.com/apps/boring-cyborg)**
2. After installing the Github app, create `.github/boring-cyborg.yml` in the default branch to enable it
3. It will start scanning for pull requests within few minutes.
```yaml
##### Labeler ##########################################################################################################
# Enable ""labeler"" for your PR that would add labels to PRs based on the paths that are modified in the PR.
labelPRBasedOnFilePath:
# Add 'label1' to any changes within 'example' folder or any subfolders
label1:
- example/**/*
# Add 'label2' to any file changes within 'example2' folder
label2:
- example2/*
# Complex: Add 'area/core' label to any change within the 'core' package
area/core:
- src/core/*
- src/core/**/*
# Add 'test' label to any change to *.spec.js files within the source dir
test:
- src/**/*.spec.js
##### Greetings ########################################################################################################
# Comment to be posted to welcome users when they open their first PR
firstPRWelcomeComment: >
Thanks for opening this pull request! Please check out our contributing guidelines.
# Comment to be posted to congratulate user on their first merged PR
firstPRMergeComment: >
Awesome work, congrats on your first merged pull request!
# Comment to be posted to on first time issues
firstIssueWelcomeComment: >
Thanks for opening your first issue here! Be sure to follow the issue template!
###### IssueLink Adder #################################################################################################
# Insert Issue (Jira/Github etc) link in PR description based on the Issue ID in PR title.
insertIssueLinkInPrDescription:
# specify the placeholder for the issue link that should be present in the description
descriptionIssuePlaceholderRegexp: ""^Issue link: (.*)$""
matchers:
# you can have several matches - for different types of issues
# only the first matching entry is replaced
jiraIssueMatch:
# specify the regexp of issue id that you can find in the title of the PR
# the match groups can be used to build the issue id (${1}, ${2}, etc.).
titleIssueIdRegexp: \[(AIRFLOW-[0-9]{4})\]
# the issue link to be added. ${1}, ${2} ... are replaced with the match groups from the
# title match (remember to use quotes)
descriptionIssueLink: ""[${1}](https://issues.apache.org/jira/browse/${1}/)""
docOnlyIssueMatch:
titleIssueIdRegexp: \[(AIRFLOW-X{4})\]
descriptionIssueLink: ""`Document only change, no JIRA issue`""
###### Title Validator #################################################################################################
# Verifies if commit/PR titles match the regexp specified
verifyTitles:
# Regular expression that should be matched by titles of commits or PR
titleRegexp: ^\[AIRFLOW-[0-9]{4}\].*$|^\[AIRFLOW-XXXX\].*$
# If set to true, it will always check the PR title (as opposed to the individual commits).
alwaysUsePrTitle: true
# If set to true, it will only check the commit in case there is a single commit.
# In case of multiple commits it will check PR title.
# This reflects the standard behaviour of Github that for `Squash & Merge` GitHub
# uses the PR title rather than commit messages for the squashed commit ¯\_(ツ)_/¯
# For single-commit PRs it takes the squashed commit message from the commit as expected.
#
# If set to false it will check all commit messages. This is useful when you do not squash commits at merge.
validateEitherPrOrSingleCommitTitle: true
# The title the GitHub status should appear from.
statusTitle: ""Title Validator""
# A custom message to be displayed when the title passes validation.
successMessage: ""Validation successful!""
# A custom message to be displayed when the title fails validation.
# Allows insertion of ${type} (commit/PR), ${title} (the title validated) and ${regex} (the titleRegexp above).
failureMessage: ""Wrong ${type} title: ${title}""
###### PR/Branch Up-To-Date Checker ####################################################################################
# Check if the branch is up to date with master when certain files are modified
checkUpToDate:
# The default branch is ""master"", change the branch if you want to check against a different target branch
targetBranch: master
files:
# File paths that you want to check for
# In this example, it checks if the branch is up to date when alembic migrations are modified in the PR.
# It helps avoid multiple heads in alembic migrations in a collaborative development project.
- airflow/migrations/*
- airflow/migrations/**/*
- airflow/alembic.ini
```
All the features are optional. Simply add the config for the feature you want to use.
If you are having issues with the GitHub app not working, please create an issue on https://github.com/kaxil/boring-cyborg/issues.
","https://github.com/kaxil/boring-cyborg","2020/1/4 23:52:58","2020/3/13 21:08:37","{'checks': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'single_file': 'read', 'statuses': 'write'}","['issues', 'label', 'pull_request', 'pull_request_review', 'pull_request_review_comment']"
"123","135","sourcelevel-bot","sourcelevel","39925474","Organization","SourceLevel Bot","This GitHub Integration makes easy to install [SourceLevel](https://sourcelevel.io/?utm_medium=app&utm_source=github&utm_campaign=githubapp) into your GitHub repositories, enabling automatic code review of your repositories.
## Usage
1. **[Install the integration on your GitHub account or on an organization](https://github.com/apps/sourcelevel-bot/installations/new)**
2. Visit your **[SourceLevel dashboard](https://sourcelevel.io/?utm_medium=app&utm_source=github&utm_campaign=githubapp)** and finish the setup for the repositories you want SourceLevel to start reviewing.
After finishing step 2, The `sourcelevel-bot` account will start reviewing the Pull Requests of your repositories, providing actionable feedback on your code and helping your team to ship better code faster.
![https://marketing.sourcelevel.io/github/review.png](https://marketing.sourcelevel.io/github/review.png)
#### First Pull Request
![https://marketing.sourcelevel.io/github/pull-request-introduction.png](https://marketing.sourcelevel.io/github/pull-request-introduction.png)
#### Automatic Code Review
![https://marketing.sourcelevel.io/github/pull-request-comment.png](https://marketing.sourcelevel.io/github/pull-request-comment.png)
## Already using SourceLevel?
If you are already using SourceLevel through an OAuth2 token, you can install the integration, migrate the installation to an existing SourceLevel account and upgrade any repositories being reviewed by SourceLevel from our WebHook to the Integration flow. See our **[documentation page](https://docs.sourcelevel.io/guides/getting-started/installing-github-app/?utm_medium=app&utm_source=github&utm_campaign=githubapp#migrating-your-installation-to-an-existing-sourcelevel-account)** for more details.
## Need any help?
You can learn how to configure SourceLevel to better review your codebase by checking our **[documentation](https://docs.sourcelevel.io?utm_medium=app&utm_source=github&utm_campaign=githubapp)**.","https://sourcelevel.io/?utm_medium=app&utm_source=github&utm_campaign=githubapp","2016/11/8 19:24:59","2019/10/23 13:40:05","{'administration': 'read', 'contents': 'read', 'issues': 'read', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['issue_comment', 'membership', 'public', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'repository', 'team']"
"124","136","mistaken-pull-closer","probot","26350515","Organization","Mistaken Pull Closer","a GitHub App built with probot that automatically closes pull requests that are commonly mistakes.","https://github.com/probot/mistaken-pull-closer","2017/11/10 20:16:10","2017/11/10 20:18:49","{'members': 'read', 'metadata': 'read', 'pull_requests': 'write', 'single_file': 'read'}","['pull_request']"
"125","138","google-ml-butler","tensorflowbutler","28546240","User","Google-ML-Butler","","https://github.com//tensorflow-butler","2019/10/15 20:29:19","2021/6/2 19:02:15","{'checks': 'read', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'read'}","['check_run', 'issues', 'issue_comment', 'label', 'pull_request', 'pull_request_review']"
"126","139","update-docs","probot","26350515","Organization","Update Docs","# update-docs
> a GitHub App built with [probot](https://github.com/probot/probot) that comments on newly opened Pull Requests that do not update either the README or a file in the `/docs` folder.
<img width=""810"" alt=""screen shot 2017-07-12 at 2 59 22 pm"" src=""https://user-images.githubusercontent.com/13410355/28179044-97207bee-67b5-11e7-80d0-0c8ede4a325f.png"">
## Usage
1. Install the bot on the intended repositories. The plugin requires the following **Permissions and Events**:
- Pull requests: **Read & Write**
- [x] check the box for **Pull Request** events
2. Add a `.github/config.yml` file that contains the contents you would like to reply within an `updateDocsComment`
3. Optionally, you can also add a `whiteList` that includes terms, that if found in the title, the bot will not comment on.
```yml
# Configuration for update-docs - https://github.com/behaviorbot/update-docs
# Comment to be posted to on PRs that don't update documentation
updateDocsComment: >
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would update some of our documentation based on your changes.
updateDocsWhiteList:
- bug
- chore
```","https://probot.github.io/apps/update-docs/","2017/8/4 17:42:43","2017/9/28 16:07:04","{'metadata': 'read', 'pull_requests': 'write', 'single_file': 'read'}","['pull_request']"
"127","140","squash-labs","squashlabs","39679465","User","Squash Labs","A better way to test web apps. Squash creates a virtual machine for each branch of code and automatically makes your app available from a unique URL.","https://squash.io/","2017/6/26 08:38:27","2019/3/6 22:44:06","{'contents': 'read', 'members': 'read', 'metadata': 'read', 'organization_projects': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['organization', 'pull_request', 'push', 'repository']"
"128","141","cmty","cmty","31626411","Organization","CMTY","Create your Open Source Community","https://cmty.app","2017/10/25 14:31:37","2018/6/4 14:23:15","{'administration': 'read', 'contents': 'read', 'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'read', 'statuses': 'read'}","['issues', 'issue_comment', 'membership', 'public', 'pull_request', 'push', 'release', 'repository', 'watch']"
"129","142","shortcut-integration","useshortcut","1672820","Organization","Shortcut Integration","Link your GitHub changes to Shortcut Stories.","https://shortcut.com/","2016/8/14 01:54:38","2021/9/8 17:37:37","{'contents': 'read', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'read'}","['create', 'delete', 'issues', 'issue_comment', 'label', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'push', 'repository', 'status']"
"130","143","buildsize","Daniel15","91933","User","BuildSize","BuildSize is a simple way to automatically track the size of your build artifacts. For each pull request you receive, BuildSize will automatically calculate the size of the build artifacts, and leave a comment (and a build status message) comparing them to the latest master version.","https://buildsize.org/","2017/9/3 05:14:14","2017/9/5 01:00:31","{'contents': 'read', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['create', 'pull_request', 'push', 'status']"
"131","144","sofastack-bot","sofastack-bot","49505456","User","SOFAStack-bot","Rebot of SOFAStack™.","https://www.sofastack.tech","2019/4/25 12:56:54","2019/6/18 07:24:58","{'administration': 'write', 'checks': 'write', 'contents': 'write', 'deployments': 'write', 'issues': 'write', 'members': 'write', 'metadata': 'read', 'organization_hooks': 'write', 'pull_requests': 'write', 'repository_hooks': 'write', 'statuses': 'write'}","['check_run', 'check_suite', 'commit_comment', 'create', 'delete', 'deployment', 'deployment_status', 'fork', 'issues', 'issue_comment', 'label', 'member', 'membership', 'organization', 'pull_request', 'pull_request_review', 'push', 'release', 'repository', 'status', 'team', 'watch']"
"132","145","nx-cloud","nrwl","23692104","Organization","Nx Cloud","The [Nx Cloud](https://nx.app) GitHub App lets you [access the result of every run — with all its logs and build insights](https://bit.ly/33Um32e) — straight from your PR.
![NxCloud Screenshot](https://user-images.githubusercontent.com/5975076/129180273-2952fd86-c6e6-4b73-80c9-828f413d03b5.png)
The app gives you a consolidated view for distributed CI runs and allows you to filter your runs to quickly find the failed tasks.
![Run View Example](https://user-images.githubusercontent.com/5975076/129180358-1b6975b4-65ea-4589-a456-e29a1f03a0dc.png)
For most CI systems there is nothing you need to do after installing the app. For some, you need to define the NX_BRANCH env variable (learn more [here](https://nx.app/docs/public-cloud-github-integration)).
## Learn More
* [Learn about Nx](https://nx.dev)
* [Learn about Nx Cloud](https://nx.app)
","https://nx.app","2020/9/10 14:10:32","2021/8/12 10:16:55","{'checks': 'write', 'contents': 'read', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write'}","['check_suite', 'pull_request']"
"133","146","realm-probot","realm-ci","7657856","User","realm-probot","A bot that takes care of automating tasks based on events happening on Github and Zenhub","https://realm.io","2018/6/25 09:20:18","2018/6/25 12:28:12","{'issues': 'write', 'members': 'read', 'metadata': 'read', 'pull_requests': 'write'}","['issues', 'pull_request', 'watch']"
"134","7","greenkeeper","greenkeeperio","13812225","Organization","Greenkeeper","☝️ **Important announcement:** Greenkeeper will be saying goodbye ? and passing the torch to Snyk on June 3rd, 2020! New installations are no longer possible. [Find out how to migrate to Snyk and more at greenkeeper.io](https://greenkeeper.io)
## Help and support
If you have questions or require support, please consult our [FAQ](https://greenkeeper.io/faq.html), it also contains contact information for our support team.","https://greenkeeper.io","2016/10/24 20:19:55","2020/6/3 11:10:26","{'checks': 'read', 'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'write', 'vulnerability_alerts': 'read'}","['check_run', 'check_suite', 'delete', 'issues', 'issue_comment', 'public', 'pull_request', 'pull_request_review', 'pull_request_review_comment', 'push', 'repository', 'status']"
"135","59","pull","wei","5880908","User","Pull","<p align=""center"">
<a href=""https://github.com/apps/pull"">
<img alt=""Pull App"" src=""https://prod.download/pull-social-svg"" />
</a>
</p>
<p align=""center"">
<a href=""https://probot.github.io"">
<img alt=""Probot Featured"" src=""https://badgen.net/badge/probot/featured/orange?icon=dependabot&style=flat&cache=86400"" />
</a>
<a href=""https://github.com/wei/pull"">
<img alt=""GitHub Stars"" src=""https://badgen.net/github/stars/wei/pull?icon=github&cache=600"" />
</a>
<br/>
<a href=""https://github.com/apps/pull"">
<img alt=""Managing"" src=""https://badgen.net/https/raw.githack.com/pull-app/stats/master/badges/managing.json?cache=600"" />
</a>
<a href=""https://github.com/apps/pull"">
<img alt=""Installations"" src=""https://badgen.net/https/raw.githack.com/pull-app/stats/master/badges/installed.json?cache=600"" />
</a>
<a href=""https://github.com/issues?q=author%3Aapp%2Fpull"">
<img alt=""Triggered #"" src=""https://badgen.net/runkit/pull-triggered-badge-5e55hqhkhmid?cache=600"" />
</a>
</p>
> ? a GitHub App that keeps your forks up-to-date with upstream via automated pull requests.
**Prerequisites**
- :warning: _Make a backup if you've made changes._
- **[⭐ Star this project](https://github.com/wei/pull)** (Highly recommended, starred users may receive priority over regular users)
**Basic Setup**
- Just hit install.
Pull app will automatically watch and pull in upstream's default (master) branch to yours with **hard reset**.
For advanced setup and customizations, please visit [wei/pull](https://github.com/wei/pull#readme).","https://wei.github.io/pull","2018/6/1 00:13:40","2020/10/24 01:16:10","{'contents': 'write', 'issues': 'write', 'metadata': 'read', 'pull_requests': 'write', 'statuses': 'read', 'workflows': 'write'}","['pull_request_review']"
Reference in New Issue View Git Blame Copy Permalink