Step 2. Set Up Your GitHub Token and Collect Your
Information

Follow the steps in the GitHub documentation to create a new (OAuth 2) token with the
following scopes (permissions): admin:repo_hook and repo. If you already have a
token with these permissions, you can use that. You can find a list of all your
personal access tokens in https://github.com/settings/tokens.

Make a note of the following information:

GitHub token name.

GitHub repository name – This repository should have the folder
structure and files described earlier in the Prerequisites section.

Source branch name – This is the branch that CodePipeline
should monitor for any changes.

Release branch name – This is the branch that the source branch
will be merged into after a successful test.

You will be prompted for this information when you launch the Quick
Start.

Javascript is disabled or is unavailable in your
browser.

To use the AWS Documentation, Javascript must be
enabled. Please refer to your browser's Help pages for instructions.