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: CONTRIBUTING.md
+21-32Lines changed: 21 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,26 +12,20 @@ Read our [Code of Conduct](CODE_OF_CONDUCT.md) before contributing.
12
12
13
13
We use [Github Flow](https://guides.github.com/introduction/flow/index.html), so all code changes happen through pull requests. [Learn more.](https://blog.scottlowe.org/2015/01/27/using-fork-branch-git-workflow/))
14
14
15
-
1.Please make sure there is an issue associated with the work that you're doing. If it doesn’t exist, [create an issue.](https://github.com/testsigmahq/testsigma-tutorials/issues/new/choose)
16
-
17
-
2.If you're working on an issue, please comment that you are doing so to prevent duplicate work by others also.
18
-
19
-
3.Fork the repo and create a new branch from the `main` branch.
20
-
21
-
4.Please name the branch as issue-[issue-number]-[issue-name(optional)]. For example, if you are fixing Issue #205 name your branch as issue-205 or issue-205-how to-automate-date-widget
22
-
23
-
6.Squash your commits and refer to the issue using `Fix #<issue-no>` in the commit message, at the start.
24
-
25
-
7.Rebase `main` with your branch and push your changes.
-3. Create a branch `git checkout -b issue-[issue-number]-[issue-name(optional)]`
32
-
-4.`cd testsigma-tutorials`
33
-
-5.`npm install`
34
-
-6.`npm start`
15
+
1. Please make sure there is an issue associated with the work that you're doing. If it doesn’t exist, [create an issue.](https://github.com/testsigmahq/testsigma-tutorials/issues/new/choose)
16
+
2. If you're working on an issue, please comment that you are doing so to prevent duplicate work by others also.
17
+
3. Fork the repo and create a new branch from the `main` branch.
18
+
4. Please name the branch as issue-[issue-number]-[issue-name(optional)]. For example, if you are fixing Issue #205 name your branch as issue-205 or issue-205-how to-automate-date-widget
19
+
6. Squash your commits and refer to the issue using `Fix #<issue-no>` in the commit message, at the start.
20
+
7. Rebase `main` with your branch and push your changes.
3. Create a branch `git checkout -b issue-[issue-number]-[issue-name(optional)]`
26
+
4.`cd testsigma-tutorials`
27
+
5.`npm install`
28
+
6.`npm start`
35
29
36
30
Now you can access tutorials on your local server using http://localhost:8000/tutorials/
37
31
@@ -42,22 +36,17 @@ The main branch (protected) contains the code that is tested and released. Pull
42
36
43
37
Once you are done with the code changes on your local machine, follow the below steps to commit.
44
38
45
-
### Commit & Create Pull Requests
46
-
47
-
1.Please make sure there is an issue associated with the work that you're doing. If it doesn’t exist, [create an issue.](https://github.com/testsigmahq/testsigma-tutorials/issues/new/choose)
48
-
49
-
2.Squash your commits and refer to the issue using `Fix #<issue-no>` in the commit message, at the start.
50
-
51
-
3.Rebase `main` with your branch and push your changes.
52
-
53
-
4.Once you are confident in your code changes, create a pull request in your fork to the main branch in the testsigmahq/testsigma-tutorials base repository.
54
-
55
-
5.Link the issue of the base repository in your Pull request description. [Guide](https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)
39
+
#### **Commit & Create Pull Requests**
40
+
1. Please make sure there is an issue associated with the work that you're doing. If it doesn’t exist, [create an issue.](https://github.com/testsigmahq/testsigma-tutorials/issues/new/choose)
41
+
2. Squash your commits and refer to the issue using `Fix #<issue-no>` in the commit message, at the start.
42
+
3. Rebase `main` with your branch and push your changes.
43
+
4. Once you are confident in your code changes, create a pull request in your fork to the main branch in the testsigmahq/testsigma-tutorials base repository.
44
+
5. Link the issue of the base repository in your Pull request description. [Guide](https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)
56
45
57
46
For all contributions, a CLA (Contributor License Agreement) needs to be signed [here](https://cla-assistant.io/testsigmahq/testsigma-tutorials) before (or after) the pull request has been submitted. A bot will prompt contributors to sign the CLA via a pull request comment, if necessary.
58
47
59
48
60
-
###Commit messages
49
+
#### **Commit messages**
61
50
62
51
- The first line should be a summary of the changes, not exceeding 50
63
52
characters, followed by an optional body that has more details about the
0 commit comments