docs: extra information regarding endpoint creation. (#44)

Author: hydra

README.md

@@ -87,7 +87,7 @@ This option is one of the mandatory fields to allow GitHub Tool interact with Gi
 
 #### 1. Authorize using OAuth
 
-This service provides you direct and fast connection with GitHub authentication. If you need to modify some access and grant new authorizations you will have to access your GitHub acoount, go to `Settings` > `Applications` > `Authorized OAuth Apps`, found `Visual Studio Team Services` and modify permissions and organization access.
+This service provides you direct and fast connection with GitHub authentication. If you need to modify some access and grant new authorizations you will have to access your GitHub acoount, go to `Settings` > `Applications` > `Authorized OAuth Apps`, found `Azure Pipelines (OAuth)` and modify permissions and organization access.
 
 #### 2. Authorize with a GitHub personal access token
 
@@ -98,6 +98,10 @@ This option needs a personal access token from GitHub, you can create it by goin
 | repo  | Allow access to private repositories  |
 | public_repo  | Allow access to public repositories  |
 
+### Creating service endpoints
+
+Service endpoints can be created from the Azure Devops project dashboard, login and go to `Project Settings` > `Service connections` > `New service connection`.  Select `Github` from the list.  Chose authentication method (e.g. `OAuth` or  `Personal Access Token`). Then `Authorsize`, then Complete other details and finall `Save`.
+
 ## Why?
 
 I was disappointed with all the current GitHub extensions tools solutions. Most of them don't have most of the options GitHub can provide and don't are maintained anymore. So, I found [publish-release](https://github.com/remixz/publish-release) repository with almost every option that I need, helped them to finish some issues and use that to create this extension for Azure DevOps Releases and Builds.