let's set up the GitHub spoke to integrate your 
instance with GitHub and the GitHub Enterprise   server connecting your instance with one 
or both servers can help automate flows   and perform actions we'll follow along as able 
an administrator sets up GitHub and the GitHub   Enterprise server for his company AEL starts 
on the GitHub dashboard where he selects the   profile icon next he selects settings on the 
settings page able selects developer settings   navigates to personal access tokens and chooses 
tokens classic then selects generate new token   classic in the note field he enters the 
description of the personal access token   in the expiration field he enters the expiration 
period of the token in this case the expiration   date will occur in 30 days under the select Scopes 
heading AEL selects the Scopes that Define the   access for the personal access token he needs 
in this case he selects the repo user and delete   uncore repo Scopes next he clicks generate token 
and copies the personal access token AEL makes   sure to save the personal access token now as he 
won't be able to see it again now AEL can set up   the connection record to connect his company's 
instance with GitHub he navigates to workflow Studio and selects Integrations in the search 
all connections field he enters GitHub to create   the GitHub connection he selects the GitHub 
connection card he selects view details then   configure from here he fills in the connection 
name connection URL use mid server and API key   Fields GitHub is the default and readon name 
of the first connection record the default   connection URL is included as well able 
enters zero because his company's service   now instance doesn't require a mid server to 
connect with GitHub then he adds the personal   access token he generated earlier next he clicks 
configure connection and the GitHub connection   record is created now AEL will create the GitHub 
Enterprise server connection to create this he   needs to generate another personal access 
token on the GitHub Enterprise server he   goes to the GitHub Enterprise dashboard 
and selects the profile icon then user   settings from here he repeats the same steps 
he'd use to generate the personal access token in this case he selects the repo and user Scopes now he can generate the token like 
the personal access token created for the   first GitHub connection he copies the token as 
he won't be able to see it again he navigates   back to the instance and selects the GitHub 
server connection card selects view details   and fills in the form in this case because it's 
the first connection record the default name is   GitHub server in the connection URL field AEL 
enters the URL of his GitHub instance next he   enters a zero in the use mid server field as 
his instance doesn't require a mid server to   connect with the GitHub Enterprise server then he 
enters the API key he copied earlier and clicks   configure connection the GitHub Enterprise Server 
Connection record is created AEL has integrated   his company's instance with the GitHub and 
GitHub Enterprise server to learn more see   our product documentation or knowledge base 
or ask a question in the service now community