Skip to content

Commit 4ae96cc

Browse files
committed
Add documentation for the GitHub integration #349
Signed-off-by: tdruez <tdruez@nexb.com>
1 parent 320e66d commit 4ae96cc

2 files changed

Lines changed: 81 additions & 0 deletions

File tree

docs/index.rst

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,12 @@ Welcome to the very start of your DejaCode journey!
4444
reference-2
4545
reference-3-cravex
4646

47+
.. toctree::
48+
:maxdepth: 1
49+
:caption: Integrations
50+
51+
integrations-github
52+
4753
.. toctree::
4854
:maxdepth: 1
4955
:caption: Miscellaneous

docs/integrations-github.rst

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
.. _integrations_github:
2+
3+
GitHub Integration
4+
==================
5+
6+
DejaCode's integration with GitHub allows you to automatically forward
7+
**Workflow Requests** to GitHub repository **Issues**.
8+
This behavior can be selectively applied to any **Request Template** of your choice.
9+
10+
GitHub Account and Personal Access Token
11+
----------------------------------------
12+
13+
To enable integration, you need a GitHub **fine-grained personal access token (PAT)**.
14+
15+
1. **Access GitHub Developer Settings**:
16+
17+
- Go to: https://github.com/settings/personal-access-tokens
18+
- Click **"Generate new token"** under *Fine-grained personal access tokens*
19+
20+
2. **Configure the Token**:
21+
22+
- **Name**: Give it a clear name (e.g., ``DejaCode Integration``)
23+
- **Expiration**: Set an expiration date (recommended)
24+
- **Resource owner**: Choose your personal GitHub account or organization
25+
26+
.. note::
27+
28+
It is recommended to **create a dedicated GitHub user** with a clear, descriptive
29+
name such as ``dejacode-integration``. This ensures that all GitHub issues managed by
30+
the integration are clearly attributed to that user, improving traceability and
31+
auditability.
32+
33+
3. **Repository Access**:
34+
35+
- Under *Repository access*, select **Only select repositories**
36+
- Choose the repository where you want issues to be created and updated
37+
38+
4. **Permissions**:
39+
40+
- Under *Repository permissions*, enable::
41+
42+
Issues: Read and write
43+
44+
5. **Save and Copy the Token**:
45+
46+
- Click **Generate token**
47+
- Copy the token and store it securely — you’ll need it for the next step
48+
49+
DejaCode Dataspace Configuration
50+
--------------------------------
51+
52+
To use your GitHub token in DejaCode:
53+
54+
1. Go to the **Administration dashboard**
55+
2. Navigate to **Dataspaces**, and select your Dataspace
56+
3. Scroll to the **GitHub Integration** section under **Configuration**
57+
4. Paste your GitHub token in the **GitHub token** field
58+
5. Save the form
59+
60+
Activate GitHub Integration on Request Templates
61+
------------------------------------------------
62+
63+
1. Go to the **Administration dashboard**
64+
2. Navigate to **Workflow** > **Request templates**
65+
3. Create or edit a Request Template in your Dataspace
66+
4. Set the **Issue Tracker ID** field to your GitHub repository URL, e.g.::
67+
68+
https://github.com/org/repo_name
69+
70+
Once the integration is configured:
71+
72+
- New **Requests** using this template will be automatically pushed to GitHub
73+
- Field updates (like title or priority) and **status changes** (e.g. closed) will be
74+
synced
75+
- New **Comments** on a DejaCode Request will be propagated to the GitHub Issue.

0 commit comments

Comments
 (0)