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
* GitHub integration how to
new screenshots and first steps
[ci skip]
* GitHub integration explanation
Added description how the new GitHub integration works including step by step screenshots
[ci skip]
Copy file name to clipboardExpand all lines: docs/system-admin-guide/github-integration/README.md
+34-53Lines changed: 34 additions & 53 deletions
Original file line number
Diff line number
Diff line change
@@ -8,34 +8,9 @@ keywords: github integration
8
8
---
9
9
# GitHub integration
10
10
11
-
OpenProject offers an integration for GitHub pull requests.
12
-
You create a pull request in GitHub and link it to an OpenProject work package.
11
+
OpenProject offers an integration for GitHub pull requests to integrate software development closely with planning and specification.
13
12
14
-

15
-
16
-
Rather than inserting a link to the work package you can also reference it just by adding "OP#87" to the pull request's description where 87 is the ID of the work package.
17
-
18
-
OpenProject will add comments to work packages about the pull request when the pull request is
19
-
20
-
* first referenced (usually when opened)
21
-
* merged
22
-
* closed
23
-
24
-

25
-
26
-
Given the right permissions on the project, a "GitHub" tab is shown for work packages. All previously linked pull requests can be seen there including the PR's status and checks (e.g. tests and linter runs).
27
-
28
-
## Configuration
29
-
30
-
You will have to configure both OpenProject and GitHub for the integration to work.
31
-
32
-
### OpenProject
33
-
34
-
In *Project settings* and *Modules* you will need to activate the GitHub module.
35
-
36
-

37
-
38
-
Then you will have a GitHub tab appearing in your work package view where you will see all information pulling through from GitHub.
13
+
OpenProject work packages will directly display information from GitHub in a separate tab.
39
14
40
15

41
16
@@ -44,59 +19,61 @@ In your OpenProject work package, the GitHub integration supports you to create
44
19
45
20

46
21
22
+
In order to create a new branch, open the GitHub tab in your OpenProject work package detail view. Click on Git snippets to extend the menu. First, copy the branch name.
And use it in the GitHub desktop commmit message field. Make sure you use the reference for the OpenProject work package (in this case #6006) in the title.
Subsequently, you can create your pull request. Title and comment with the link to the respective OpenProject work package will be prefilled. If you want, you can add some additional information.
When you click on the link in the comment, it will take you to the OpenProject work package, where you will see in the Activity tab of the work package that the pull request was created.
In the GitHub tab of that work package, the status of the pull request as well as the GitHub Action will be displayed.
80
63
81
-
see GitHubaction in GitHub tab
64
+

82
65
83
-
84
-
85
-
If PR is merged, it will appear in OP
86
-
87
-
88
-
89
-
If you already have an existing pull request in GitHub, you can link it using the code OP#0000 (0000 being the ID of the work package) in the GitHub pull request description.
90
-
91
-
92
-
93
-

66
+
If the status of a pull request changes, it will accordingly appear in its OpenProject work package. Please see the example below.
You will have to configure both OpenProject and GitHub for the integration to work.
75
+
76
+
### OpenProject
100
77
101
78
First you will need to create a user in OpenProject that will make the comments.
102
79
The user will have to be added to each project with a role that allows them
@@ -116,7 +93,11 @@ to use later on the GitHub side of things. For this you have to:
116
93
3. Go to Access Token
117
94
4. Click on generate in the API row
118
95
119
-
Copy the generated key. You can now configure the necessary webhook in GitHub.
96
+
Copy the generated key. You can then configure the necessary webhook in GitHub.
97
+
98
+
In addition, in *Project settings* and *Modules* you will need to activate the GitHub module so that all information pulling through from GitHub will be shown in the work packages.
0 commit comments