...

A GitHub instance looks like this:

...

Fill in the base url URL with the github GitHub username or org-based urlURL. This url URL should be the one that your projects are sourced out of.

...

Creating an OAuth Token for FlexDeploy ITS

Excerpt
name OAuth
Go to GitHub and login as the user you want to comment on GitHub Issues with. Generate a Personal Access Token in Github following this guide: https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token Choose an expiration date based on your security policies. Shorter expiration dates will require updating the ITS more frequently. Choose the following OAuth scopes to comment on and change status of issues:

Setting

...

Up Folders and

...

Projects to

...

Use the GitHub ITS Instance

Then back in FlexDeploy, setup set up your folder ITS settings like this:

...

Now you are ready to link tickets with commits or by manually entering them on project builds or project packages.

Linking with

...

Commit Messages

Set up your FlexDeploy Project with a ticket pattern. The pattern must be github GitHub repo name + “-” + issue number.

...

Following this pattern, make a commit message.

...

Push and Merge merge your change.

...

When you create a build, the issue numbers are pulled from your commits.

...

Linking by Manual Entry at Project Build Time

If you didn’t remember to put the issue number in your commit, and you are building the project manually, you can enter issue numbers at build time.

The issue number should be GitHub Repo Name-Issue Number

In this example, it’s maven-project-3.

...

Linking

...

Issues to

...

Project Packages

If you don’t put issue numbers in your commits , and you are working with a package-based project, and you want to can associate issues with packages that will live through the its build and deployment lifecycle , you can follow by following this pattern.

Go to the project and package which you wish to link a GitHub Issue.

...

Add one or more Issues. The drop down dropdown only shows previously linked issues. Type the entire issue key to make a new one.

...

The issue number should be in the format GitHub Repo Name-Issue Number

Now, builds and deploys deployments of this package will be associated to that GitHub Issue.