![]() The process can be trial and error depending upon your setup. This is a good point to check your GitHub repository to see if everything is populating as intended. Once you've set up the various fields in the action step that you'd like to send over to GitHub when you create the issue you can test the automation step. Clicking the cogwheel icon next to each field will allow you to see more specifics about the dynamic setup. Static choices are limited to the options in the dropdown menu for each field, whereas dynamic values will be inputted based on information coming from previous steps in your automation's setup. Currently, there are 5 fields that are able to be customized:Īdditionally, the Milestone, Labels, and Assignees fields can be set up to be set up statically or dynamically. Next, you'll want to match the fields (or static information) from your Airtable base to the corresponding GitHub fields. You'll first need to choose one of your GitHub repositories (repos) where the issues will be stored. The installation screen will look like this:įor more on authentication and authorization, click to jump to that section below.Īfter connecting your account and installing the app, you will see the action step portion of the automation window populate with some dropdown menus. This is a requirement on GitHub's end that is needed to allow this sync to work. You will also need to install the Airtable GitHub app which you can click to download within the sync setup window or by clicking here. If this is your first time connecting Airtable to your GitHub account, then you will need to authenticate your account and authorize Airtable's usage. Click whichever action you are wanting to set up. This flow is using the example of adding the "Create issue" action, but as you can see the "Update issue" action is just below. When it runs successfully, you can then move on to the action portion of the automation. You could follow a similar workflow when setting up your base to work with the update issue automation action.Īs always, make sure you run a test. We've added a checkbox field in the "Issues" table that will serve as a good way to parse out which issues are ready to be sent over to GitHub. In this case, we choose to use the "When record matches conditions" trigger type. For this example, we will be creating a new GitHub issue, but the process is much the same for updating a GitHub issue. Then click on the option to "Create a custom automation."Īfter clicking to create a new custom automation, you will have the option to rename the option. ![]() The first step is to find the "Automations" button near the upper right portion of your Airtable base. If you’ve already started thinking about how you want to use this action in your automation, then it is time to start building in Airtable. These actions do not work with GitHub Enterprise Server. ![]() It's worth noting that these automation actions only work with GitHub Enterprise Cloud or. You might also be interested in our GitHub Sync integration offering. This article covers the process of adding an automation action that will either create a new issue or update an issue in the GitHub repository of your choice.
0 Comments
Leave a Reply. |