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: CONTRIBUTION.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ Please note we have a [code of conduct](CODE_OF_CONDUCT.md), please follow it in
6
6
7
7
## How to report bugs or feature requests
8
8
9
-
You can **create bug and feature requests** through [Sage Bionetwork's FAIR Data service desk](https://sagebionetworks.jira.com/servicedesk/customer/portal/5/group/8). Providing enough details to the developers to verify and troubleshoot your issue is paramount:
9
+
You can **create bug and feature requests** through [Sage Bionetwork's DPE schematic support](https://sagebionetworks.jira.com/servicedesk/customer/portal/5/group/7/create/225). Providing enough details to the developers to verify and troubleshoot your issue is paramount:
10
10
-**Provide a clear and descriptive title as well as a concise summary** of the issue to identify the problem.
11
11
-**Describe the exact steps which reproduce the problem** in as many details as possible.
12
12
-**Describe the behavior you observed after following the steps** and point out what exactly is the problem with that behavior.
@@ -25,7 +25,7 @@ For new features, bugs, enhancements:
25
25
26
26
#### 1. Branch Setup
27
27
* Pull the latest code from the develop branch in the upstream repository.
28
-
* Checkout a new branch formatted like so: `develop-<feature/fix-name>` from the develop branch
28
+
* Checkout a new branch formatted like so: `<JIRA-ID>-<feature/fix-name>` from the develop branch
29
29
30
30
#### 2. Development Workflow
31
31
* Develop on your new branch.
@@ -35,22 +35,22 @@ For new features, bugs, enhancements:
35
35
* You can choose to create a draft PR if you prefer to develop this way
36
36
37
37
#### 3. Branch Management
38
-
* Push code to `develop-<feature/fix-name>` in upstream repo:
38
+
* Push code to `<JIRA-ID>-<feature/fix-name>` in upstream repo:
39
39
```
40
-
git push <upstream> develop-<feature/fix-name>
40
+
git push <upstream> <JIRA-ID>-<feature/fix-name>
41
41
```
42
-
* Branch off `develop-<feature/fix-name>` if you need to work on multiple features associated with the same code base
42
+
* Branch off `<JIRA-ID>-<feature/fix-name>` if you need to work on multiple features associated with the same code base
43
43
* After feature work is complete and before creating a PR to the develop branch in upstream
44
44
a. ensure that code runs locally
45
45
b. test for logical correctness locally
46
46
c. run `pre-commit` to style code if the hook is not installed
47
47
c. wait for git workflow to complete (e.g. tests are run) on github
48
48
49
49
#### 4. Pull Request and Review
50
-
* Create a PR from `develop-<feature/fix-name>` into the develop branch of the upstream repo
50
+
* Create a PR from `<JIRA-ID>-<feature/fix-name>` into the develop branch of the upstream repo
51
51
* Request a code review on the PR
52
52
* Once code is approved merge in the develop branch. The **"Squash and merge"** strategy should be used for a cleaner commit history on the `develop` branch. The description of the squash commit should include enough information to understand the context of the changes that were made.
53
-
* Once the actions pass on the main branch, delete the `develop-<feature/fix-name>` branch
53
+
* Once the actions pass on the main branch, delete the `<JIRA-ID>-<feature/fix-name>` branch
0 commit comments