Create Repository activity

An activity that creates a repository in GitHub.


Create Repository activity

Configure the Create Repository activity

Prerequisites

Good to Know

How to Start

  1. Open Process Builder.

    For information about how to open this screen, refer to Process Builder.


    Open Process Builder
  2. In Process Builder, in the Activity Library, open the GitHub tab.

    Open GitHub tab
  3. On the GitHub tab, drag the Create Repository activity onto your process.

    Drag Create Repository activity

General Configuration

Specifies the basic settings for the Create Repository activity.

Figure: General Configuration screen

General Configuration screen

Good to Know

  • Documentation for this screen is provided for completeness. The fields are mostly self-explanatory.

Fields

Field NameDefinition

Display Name

Description:
Specifies the activity name that shows in your process.
Allowed Values:
One line of text (a string).

Accepted:

  • Letters
  • Numbers
  • Spaces
Default Value:
None
Accepts Variables:
No
Example:
This is a common configuration field that is used in many examples. Refer to:
  • Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Description

Description:
Specifies an optional text description for your activity.
Allowed Values:
More than one line of text.
Default Value:
None
Accepts Variables:
No

Create Repository Configuration

Specifies the information to create a repository in GitHub.

Figure: Create Repository Configuration screen

Create Repository Configuration screen

Fields

Field NameDefinition

GitHub

Description:
Specifies the access token that connects to your GitHub service.
Allowed Values:
A list of access tokens configured for your environment.
Default Value:
None

Create Add Token icon

Opens this Screen:
Access Token for GitHub
Function of this Screen:
Configure an access token to connect to GitHub.

Repository

Description:
Specifies the name of the repository to create in GitHub.
Allowed Values:
One line of text (a string) that can have letters, numbers, spaces, and special characters.
Default Value:
None
Accepts Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

Description

Description:
Specifies a description for the repository.
Allowed Values:
More than one line of text.
Default Value:
None
Accepts Variables:
No

Invite Collaborator

Description:
Specifies one or more user names in GitHub to whom to send an invitation to access to the repository.
Allowed Values:
One or more user names in GitHub, separated by semicolons (;).
Default Value:
None
Accepts Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

Visibility

Description:
Specifies whether all users in GitHub can access the repository.
Allowed Values:
  • Public - All users in GitHub can access the repository.
  • Private - Only specified users in GitHub can access the repository.
Default Value:
Public

Store Response Repository Name In This Variable

Description:
Specifies the process data variable to store the name of the repository from GitHub.
Allowed Values:
A process data variable that accepts an alphanumeric string with no spaces or special characters. Hyphens (-) are accepted.
Default Value:
None
Accepts Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

Store Response Repository ID In This Variable

Description:
Specifies the process data variable to store the ID of the repository from GitHub.
Allowed Values:
A variable.

Format:

  • String

Accepted:

  • Numbers
Default Value:
None
Accepts Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?