Skip to content

Commit b26031b

Browse files
authored
Rebecca GitHub integration (#9354)
* 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]
1 parent a021379 commit b26031b

19 files changed

+34
-53
lines changed
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading

docs/system-admin-guide/github-integration/README.md

Lines changed: 34 additions & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -8,34 +8,9 @@ keywords: github integration
88
---
99
# GitHub integration
1010

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.
1312

14-
![New pull request linking to an OpenProject work package](github-pr-workpackage-reference.png)
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-
![Github comments on work package](workpackage-github-comments.png)
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-
![Github-module](Github-module.png)
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.
3914

4015
![GitHub-tab](GitHub-tab.png)
4116

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

4520
![GitHub-create-branch](GitHub-create-branch.png)
4621

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.
4723

24+
![GitHub-copy-branch-name](GitHub-copy-branch-name.png)
4825

49-
Copy Branch name
26+
Then, open your desktop client, e.g. GitHub desktop. There, you create your branch with the name you copied from your OpenProject work package.
5027

51-
Then open new branch in GitHub desktop
28+
![GitHub-desktop-new-branch](GitHub-desktop-new-branch.png)
5229

53-
Then go to Typora and make changes
30+
Then go to Typora (or any other editor) and create content or make changes.
5431

55-
Save
32+
![GitHub-test-copy](GitHub-test-copy.png)
5633

57-
Changes in GitHub desktop
34+
Save and the changes will appear in GitHub desktop or the client you are using.
5835

59-
in OP use commit message
36+
![GitHub-changes](GitHub-changes.png)
6037

61-
Publish branch
38+
In order to commit these changes, go to OpenProject to copy the commit message.
6239

40+
![GitHub_OpenProject-commit-message](GitHub_OpenProject-commit-message.png)
6341

42+
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.
6443

44+
![GitHub-commit](GitHub-commit-2645308.png)
6545

46+
After having committed, publish your branch.
6647

67-
create PR
48+
![GitHub-publish-branch](GitHub-publish-branch.png)
6849

69-
add info in comment
50+
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.
7051

71-
create PR green button
52+
![GitHub-open-pull-request](GitHub-open-pull-request-2645707.png)
7253

73-
click link to OP WP
54+
Click on **Create pull request** and your pull request will be opened.
7455

75-
comment in activity that PR is created
56+
![GitHub-pull-request-opened](GitHub-pull-request-opened-2646257.png)
7657

77-
commit messaage mit OP Verweis auf das AP
58+
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.
7859

60+
![GitHub-work-package-activity](GitHub-work-package-activity-2646492.png)
7961

62+
In the GitHub tab of that work package, the status of the pull request as well as the GitHub Action will be displayed.
8063

81-
see GitHub action in GitHub tab
64+
![GitHub-action](GitHub-action.png)
8265

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-
![GitHub-actions](GitHub-actions.png)
66+
If the status of a pull request changes, it will accordingly appear in its OpenProject work package. Please see the example below.
9467

9568
![GitHub-pull-request-status](GitHub-pull-request-status.png)
9669

9770

9871

72+
## Configuration
9973

74+
You will have to configure both OpenProject and GitHub for the integration to work.
75+
76+
### OpenProject
10077

10178
First you will need to create a user in OpenProject that will make the comments.
10279
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:
11693
3. Go to Access Token
11794
4. Click on generate in the API row
11895

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.
99+
100+
![Github-module](Github-module-2647262.png)
120101

121102
### GitHub
122103

Loading

0 commit comments

Comments
 (0)