You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: fern/docs/pages/tutorials/perform-external-action.mdx
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
## Introduction
2
2
3
-
In this tutorial, you'll lean how to develop a snap-in that mirrors an issue from
3
+
In this tutorial, you'll learn how to develop a snap-in that mirrors an issue from
4
4
DevRev to GitHub. This requires addition of a command that can be run from
5
5
the **Discussions** tab of an issue in DevRev, which creates an issue in GitHub.
6
6
@@ -101,7 +101,7 @@ functions:
101
101
```
102
102
103
103
The command clearly states where you can use it. For example, in the
104
-
**Discussions** tab of issues.
104
+
**Discussions** tab of issues.
105
105
106
106
It also explains the different situations and
107
107
ways in which you can make use of this command.
@@ -126,7 +126,7 @@ name (`RepoName`) before proceeding with the issue creation.
126
126
127
127
### Function logic
128
128
129
-
After creating the manifest and establishing the snap-in's logic, the next step is to define the function logic that handles business logic. Once you understand the payload structure of a command, you can proceed with its implementation.
129
+
After creating the manifest and establishing the snap-in's logic, the next step is to define the function logic that handles the business logic. Once you understand the payload structure of a command, you can proceed with its implementation.
130
130
131
131
To proceed, define the handler function for command events.
132
132
@@ -291,11 +291,11 @@ Once the code has been validated, the next steps involve creating the snap-in
291
291
version and subsequently creating the snap-in itself. Before installing the
292
292
snap-in, it's essential to set up a GitHub Personal Access Token (PAT) and add
293
293
it to the connections in DevRev as a snap-in secret. Ensure that the secret is
294
-
shared within the organization so that the snap-in can utilize it.
294
+
shared within the organization so that the snap-in can utilize it.
295
295
296
296
Follow these steps to install the snap-in in your organization:
297
297
298
-
#### Step 1: Create a GitHub personal access token
298
+
#### Step 1: Create a GitHub personal access token
299
299
300
300
Generate a GitHub Personal Access Token (PAT) by following the steps outlined in the
0 commit comments