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: .github/CONTRIBUTING.md
+11-7Lines changed: 11 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,18 @@
1
-
# Contributing to coteafs-selenium.
1
+
# Contributing to <project-name>.
2
2
3
3
:+1::tada: Firstly, thanks for taking the time to contribute! :tada::+1:
4
4
5
-
The following are set of guidelines for contributing towards this framework on Github. These are mostly guidelines, not rules. Use your best judgement, and feel free to propose changes to this document in a pull request.
5
+
The following are the set of guidelines for contributing towards this repository on Github. These are mostly guidelines
6
+
, not rules. Use your best judgement, and feel free to propose changes to this project in a pull request.
6
7
7
8
## Code Contribution
8
9
9
10
## 1. Where to start from?
10
11
11
-
If you've noticed a bug or have a question plesae check the [search the issue tracker][tracker] to see if someone else has already created a ticket. If not, go ahead and [add one][new issue]!
12
+
If you've noticed a bug or have a question, then kindly [search the issue tracker][tracker] to see if someone
13
+
else has already created a ticket. If not, go ahead and [add one][new issue]!
12
14
13
-
## 2. Want to fix an issue or add new feature?
15
+
## 2. Want to fix an issue or add a new feature?
14
16
15
17
If this is something you think you can fix, then follow the following steps:
16
18
@@ -28,7 +30,7 @@ To Fork and clone the repository, see this useful [post][fork].
28
30
29
31
### Step 4: Create new Branch
30
32
31
-
Now create a new branch with descriptive name in your forked repo. Refer [here][branch] to know about Git branches.
33
+
Now create a new branch with a descriptive name in your forked repo. Refer [here][branch] to know about Git branches.
32
34
33
35
### Step 5: Commit with a descriptive message
34
36
@@ -51,7 +53,9 @@ There is a process in place to help maintain the quality of the framework. To ad
51
53
52
54
### Git workflow
53
55
54
-
Since the repository is hosted on GitHub, it has been configured to only accept **signed commits** from any contributor (_including me :wink:_). So make sure to **sign your commits** before sending Pull Request, **else the it will be rejected**. To know more about signed commits, check out this [post][sign-commit].
56
+
Since the repository is hosted on GitHub, it has been configured to only accept **signed commits** from any
57
+
contributor (_including me :wink:_). So make sure to **sign your commits** before sending Pull Request, **else the
58
+
PR will be rejected**. To know more about signed commits, check out this [post][sign-commit].
55
59
56
60
### Branching strategy
57
61
@@ -70,7 +74,7 @@ Any work being done on any open tickets, should be done in a new branch with nam
70
74
71
75
Any Pull Request raised should make sure following checks are successful:
72
76
- Pull Request is raised to merge changes to `develop` branch.
0 commit comments