anchor.diff:      <pre>
         mutation CreateGitHubProvider {
           ssoProviderCreate(input:{
  -          organizationId:"<paste your organization id here>",
  +          organizationId:"&lt;paste your organization id here&gt;",
             type:GITHUB_OAUTH,
             githubOrganizationName:"buildkite"
           }) {
             ssoProvider {
               id
               url
  -            ...on SSOProviderGithubOAuth {
  -              githubOrganizationName
  -            }
             }
           }
         }</pre>
  
positive.code: mutation UpdateProvider {
    ssoProviderUpdate(input:{
      id:"<paste your provider id here>",
      note: "\:ruby\: Ruby team, please sign in here"
      sessionDurationInHours: 72
    }) 
  }
  
negative.code: }
  ```
  
  The provider update mutation can also be used to update your provider data if it changes.
  
  ### Part 4 of 5: Test the login flow
  
  Test the login flow with your new SSO provider. Ensure that a user can successfully complete the new authentication and gain access to your Buildkite organization before continuing. The next step, enabling your provider, will return an error if a successful test has not occurred.
  
  ### Part 5 of 5: Enable the provider for your organization
  
  After testing that the new authorization URL works and can log in a user with the correct email domain, you can enable the SSO provider for your Buildkite organization.
  
  Use the provider enable mutation with your provider id:
  
  ```graphql
  mutation EnableProvider {
    ssoProviderEnable(
      input:{
        id:"<paste your provider id here>"
      }
    ) {
      ssoProvider {
        state
      }
    }
  }
  ```
  
  Updates cannot be completed while a provider is enabled; to make changes to your provider, you will need to disable it, make your changes, then re-test and re-enable the provider.
  
  ## Advanced configuration
  
  