probot VS apps

Since smee.io was designed to work with Probot for enabling development of GitHub applications it works very well with GitHub webhooks and its UI is somewhat tailored for use with GitHub (parsing GitHub specific headers); however, if you want to leverage smee.io for other services that use webhooks you may hit a few snags.

A GitHub App built with Probot that This app alerts you of good first issues.

I'd recommend using Probot: https://github.com/probot/probot

You can create GitHub Apps in different programming languages and register them under your personal account or organization. I'm going to show you how to build a GitHub App in under 5 minutes, using the Probot app framework. Probot is a framework for building GitHub Apps in Node.js. It aims to eliminate all the drudgery–like receiving and validating webhooks, and doing authentication handstands–so you can focus on the features you want to build.

The easiest marketplace solution available for GitHub bots is Probot. We already discussed some great GitHub bots for every open-source project in the last article. Now, it's time to move a step forward and learn how to install, enable and customize these GitHub bots with an easy example.

Probot is a Node.js framework used to create GitHub Apps. Probot monitors webhook events in a repository or organization, such as commenting on a pull request, creating a new issue, submitting a pull request, reviewing code, and so on.

Are you talking about merging the branches automatically on GitHub not locally? if that what are you talking about,then probot could help you, https://probot.github.io/ maybe you can find something in the marketplace that fit your request.

Access token is the simple way to authenticate to the Rest API. You simply need to go to your GitHub account settings then Developer Settings (or simply go to this URI), and then create an access token. You can either choose the classic tokens (no restriction) or the fine-grained token where you can use fine-tuned permissions.

Go to the GitHub Apps and select to create a new GitHub App

GitHub has tucked the personal access tokens admin in a slightly hard-to-find location. From anywhere in GitHub, you can click on your profile image → Settings → Developer Settings → Personal Access Tokens.

When you're on https://github.com/settings/apps (GitHub Apps) there will be an action list button called "Personal access tokens".

In your Github Settings, go to Developer settings. Then, in Personal access tokens, Generate a new classic token with scope: write:packages

To create your GithubProvider ID and SECRET, navigate to your GitHub account developer settings and click on the OAuth Apps tab to register a new application.

Github project is needed to authenticate users. You may do so by visiting https://github.com/settings/apps. Note the Client ID and Client secret. Also, set two Callback URLs for project and contributor authentication.

In my previous post, I developed a GitHub App. I found the app at this location:https://github.com/settings/apps to edit it. In the Permissions and Events tab, I updated the user permissions and the events I wanted my app to subscribe to. In this case, I wanted my app to listen to and have access to when a user starred the repository.

Next we need to go to https://github.com/settings/apps/new to configure the integration. Fill the fields as follows: