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: docs/development-setup/02-contribution-guidelines.md
+15-19Lines changed: 15 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,28 +4,24 @@ sidebar_position: 2
4
4
5
5
# Contribution Guidelines
6
6
7
-
## Versions
7
+
We’re excited that you want to contribute to the wwWallet ecosystem! 🎉 Contributing is a great way to collaborate with the community and help improve the project. To ensure a smooth process, we’ve outlined everything you need to know in our comprehensive **Contribution Guidelines**.
8
8
9
-
We follow a loose https://semver.org/ policy.
9
+
Our Contribution Guidelines cover the following:
10
10
11
-
```
12
-
Given a version number MAJOR.MINOR.PATCH, increment the:
13
-
1. MAJOR version when you make incompatible API changes
14
-
2. MINOR version when you add functionality in a backward compatible manner
15
-
3. PATCH version when you make backward compatible bug fixes
16
-
```
11
+
-**Development Workflow**: Learn how to get started, from creating issues to submitting pull requests.
12
+
-**Pull Request Guidelines**: Understand the best practices for submitting changes, respecting architectural decisions, and using templates.
13
+
-**Code Reviews**: See how our core team ensures quality and consistency across the project.
17
14
18
-
## Development
15
+
You can find the full guidelines on our GitHub repository here:
19
16
20
-
We encourage using the `dc4eu` branch and treating it like the `main`. Development usually adheres to the following steps:
21
-
1. Create or pick an issue
22
-
2. Create a corresponding branch (on all the affected repositories)
23
-
3. Commit your changes: You can reference the relevant issue number and the type of the commit (feat, fix, style, refactor, test, docs), e.g. `docs: Update README, close #45`
24
-
4. Push your branch
25
-
5. Submit a pull request (PR)
26
-
6. Participate in the review process
27
-
7. Wait for merging or merge a reviewed PR
17
+
➡️ **[View the Contribution Guidelines on GitHub](https://github.com/wwWallet/.github/blob/main/CONTRIBUTING.md)**
28
18
29
-
## Git Actions
19
+
---
20
+
21
+
## 💬 Questions or Feedback?
22
+
23
+
If you have questions or want to share ideas, feel free to join the conversation in our **[GitHub Discussions](https://github.com/wwWallet/wallet-ecosystem/discussions)** or reach out through appropriate channels.
24
+
25
+
---
30
26
31
-
Pushing (or merging) to specific branches will trigger the creation of tagged releases based on the version specified in the `package.json` file of the corresponding repository. The branches in question will be discussed and agreed upon collectively.
27
+
Thank you for helping make the wwWallet ecosystem better! We value your time and effort and look forward to your contributions. 🚀
0 commit comments