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
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,16 +4,16 @@ Thank you for your interest in contributing to the **Evolutionary Algorithms on
4
4
5
5
Every contribution, no matter how small—from fixing typos to implementing new features—is welcome and valued.
6
6
7
-
***
7
+
---
8
8
9
9
## 🚀 Getting Started
10
10
11
11
To ensure a smooth workflow and avoid duplicate effort, please follow these steps before starting any code work.
12
12
13
13
### 1. Claim a Task
14
14
15
-
* Check the project's **issue tracker** to find an open bug or feature to work on.
16
-
* To get a task officially assigned to you, **you must tag @Ashrockzzz2003 in a comment on the issue** you wish to work on. This is required to receive assignment confirmation.
15
+
- Check the project's **issue tracker** to find an open bug or feature to work on.
16
+
- To get a task officially assigned to you, **you must tag @Ashrockzzz2003 in a comment on the issue** you wish to work on. This is required to receive assignment confirmation.
17
17
18
18
### 2. Set Up Your Development Environment
19
19
@@ -23,7 +23,7 @@ The complete guidelines for setting up your local environment, building, and run
23
23
24
24
Please follow these steps to ensure the application runs correctly locally before proceeding with any code changes.
25
25
26
-
***
26
+
---
27
27
28
28
## 🛠 Submitting Changes (Pull Requests)
29
29
@@ -38,17 +38,17 @@ When you are ready to submit your work, please follow the standard Git workflow:
38
38
39
39
### Commit Message Guidelines
40
40
41
-
* Use a clear, descriptive title for your commits.
42
-
* The first line of the commit message should be a brief summary (under 50 characters).
43
-
***Reference the issue number** the PR is addressing (e.g., `Fix: Button layout on mobile view (#42)`).
41
+
- Use a clear, descriptive title for your commits.
42
+
- The first line of the commit message should be a brief summary (under 50 characters).
43
+
-**Reference the issue number** the PR is addressing (e.g., `Fix: Button layout on mobile view (#42)`).
44
44
45
-
***
45
+
---
46
46
47
47
## 🛡 Code of Conduct
48
48
49
49
To ensure a welcoming and friendly community, we expect all contributors to follow our **Code of Conduct** (CoC) in all project spaces. Please read the CoC to understand the behavioral standards and reporting procedures.
0 commit comments