ZenBrowserMirrors/docs
1
0
Fork 0
mirror of https://github.com/zen-browser/docs.git synced 2025-07-07 17:05:34 +02:00
Code Issues Projects Releases Packages Wiki Activity

Corrected desktop contribution page

Browse source
This commit is contained in:
Jafeth Garro 2024-09-21 15:13:03 -06:00
parent 6626aaea72
commit 15742a2a2d
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
content/contribute/desktop.md
View file

@ -1,7 +1,7 @@
--- ---
title: Getting Started with Desktop Browser Development title: Getting Started with Desktop Browser Development
draft: false draft: false
lastmod: 2024-08-26 lastmod: 2024-09-21
--- ---
Contributing to the Zen Browser Desktop project is a great way to get involved with open-source software development. This guide will walk you through the steps to clone the project, set up your development environment, make contributions, and submit pull requests. Contributing to the Zen Browser Desktop project is a great way to get involved with open-source software development. This guide will walk you through the steps to clone the project, set up your development environment, make contributions, and submit pull requests.
@ -16,7 +16,7 @@ Before you begin, ensure you have the following tools installed:
![[building]] ![[building]]
## Step 6: Making a Contribution ## Step 7: Making a Contribution
### Types of Contributions ### Types of Contributions
@ -39,7 +39,7 @@ Before contributing, please keep the following guidelines in mind:
### How to Make a Pull Request ### How to Make a Pull Request
1. **Fork the Repository**: Create a fork of the Zen Browser repository on GitHub. 1. **Fork the Repository**: You can follow this GitHub official guide [Fork a repository - GitHub Docs](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo).
2. **Create a New Branch**: It’s a good practice to create a new branch for each feature or bug fix. 2. **Create a New Branch**: It’s a good practice to create a new branch for each feature or bug fix.