Problem Definition

Currently Bamboo requires the use of a Personal Access Token (PAT) which is not recommended by GitHub. With a PAT customers are subject to lower rate limits and the need to use a shared service account.
Also, once token is generated they need to individually add it to every linked repo that needs that access. If at any point it's entered incorrectly it will possibly lock the account.

Suggested Solution

• The goal would be to have a similar experience with GitHub like in Bitbucket DC;
• Have an option to create plan branches when a pull request is created in the repo, where as when using Bamboo with GitHub repo;
• GitHub connectivity can only be done through linked repository (problem of rate-limiting), it needs surface account;
• Ideally, with single click tags build plans because VCS has access;
• Be able to set up specs scans;
• Establish an OAuth2 connection between GitHub and Bamboo, that would transfer secret and client ID (OAuth2 is a protocol that lets external applications request authorization to private details in a user's GitHub account without accessing their password.
  • Currently, we do have that option for Jira Cloud -https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-github/
  • We also have an app in Jira for GitHub - https://marketplace.atlassian.com/apps/1219592/github-for-jira?tab=overview&hosting=cloud

Get updates and links about what’s happening with their repositories in Bamboo issues for:

• Pull Requests
• Commits
• Branches
• Builds
• Deployments