Skip to Content

GitHub Create Activity

Introduction

A GitHub Create activity, using its GitHub connection, creates object data in GitHub and is intended to be used as a target to consume data in an operation.

Create a GitHub Create Activity

An instance of a GitHub Create activity is created from a GitHub connection using its Create activity type.

To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Creating an Activity Instance in Component Reuse.

An existing GitHub Create activity can be edited from these locations:

Configure a GitHub Create Activity

Follow these steps to configure a GitHub Create activity:

Step 1: Enter a Name and Select an Object

In this step, provide a name for the activity and select an object. Each user interface element of this step is described below.

GitHub Create Activity Configuration Step 1

  • Name: Enter a name to identify the activity. The name must be unique for each GitHub Create activity and must not contain forward slashes / or colons :.

  • Select an Object: This section displays objects available in the GitHub endpoint.

    • Selected Object: After an object is selected, it is listed here.

    • Search: Enter any part of the object name into the search box to filter the list of objects. The search is not case-sensitive. If objects are already displayed within the table, the table results are filtered in real time with each keystroke. To reload objects from the endpoint when searching, enter search criteria and then refresh, as described below.

    • Refresh: Click the refresh icon Refresh icon or the word Refresh to reload objects from the GitHub endpoint. This may be useful if objects have been added to GitHub. This action refreshes all metadata used to build the table of objects displayed in the configuration.

    • Selecting an Object: Within the table, click anywhere on a row to select an object. Only one object can be selected. The information available for each object is fetched from the GitHub endpoint:

      • Name: The name of the object.

      • Description: The description of the object.

    Tip

    If the table does not populate with available objects, the GitHub connection may not be successful. Ensure you are connected by reopening the connection and retesting the credentials.

  • Continue on Error: Select to continue the activity execution if an error is encountered for a dataset in a batch request. If any errors are encountered, they are written to the operation log.

  • Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

  • Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Step 2: Select an Action

In this step, select an action. Each user interface element of this step is described below.

GitHub Create Activity Configuration Step 2

  • Select an Action: This section displays actions available in the GitHub endpoint.

    • Selected Object: The object selected in the previous step is listed here.

    • Selected Action: After an action is selected, it is listed here.

    • Search: Enter any part of the action name into the search box to filter the list of actions. The search is not case-sensitive. If actions are already displayed within the table, the table results are filtered in real time with each keystroke. To reload actions from the endpoint when searching, enter search criteria and then refresh, as described below.

    • Refresh: Click the refresh icon Refresh icon or the word Refresh to reload actions from the GitHub endpoint. This may be useful if actions have been added to GitHub. This action refreshes all metadata used to build the table of actions displayed in the configuration.

    • Selecting an Action: Within the table, click anywhere on a row to select an action. Only one action can be selected. The information available for each action is fetched from the GitHub endpoint:

      • Name: The name of the action.

      • Description: The description of the action.

    Tip

    If the table does not populate with available actions, the GitHub connection may not be successful. Ensure you are connected by reopening the connection and retesting the credentials.

  • Back: Click to temporarily store the configuration for this step and return to the previous step.

  • Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Step 3: Review the Data Schemas

Any request or response schemas are displayed. Each user interface element of this step is described below.

GitHub Create Activity Configuration Step 3

  • Data Schemas: These data schemas are inherited by adjacent transformations and are displayed again during transformation mapping.

    The GitHub connector uses the GitHub REST API. Refer to the API documentation for information on the schema nodes and fields.

  • Refresh: Click the refresh icon Refresh icon or the word Refresh to regenerate schemas from the GitHub endpoint. This action also regenerates a schema in other locations throughout the project where the same schema is referenced, such as in an adjacent transformation.

  • Back: Click to temporarily store the configuration for this step and return to the previous step.

  • Finished: Click to save the configuration for all steps and close the activity configuration.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Next Steps

After configuring a GitHub Create activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure the operation settings, which include the ability to chain operations together that are in the same or different workflows.

Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity Actions Menu in Connector Basics.

GitHub Create activities can be used as a target with these operation patterns:

A typical use case is to use a GitHub Create activity in the Two-transformation Pattern. In this example, the first transformation (Create Request) creates a request structure that is passed to the GitHub Create activity. The second transformation (Create Response) receives the response structure, which is then written to a variable by a Variable Write activity (Write Create Response) and a message is then logged by the Write to Operation Log script:

GitHub Create operation

To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.

When ready, deploy and run the operation and validate behavior by checking the operation logs.