From 24cecb1e5784128847635a3efd41dfa505787a3c Mon Sep 17 00:00:00 2001 From: oSumAtrIX Date: Fri, 23 Feb 2024 03:03:50 +0100 Subject: [PATCH] docs: Format markdown code --- CONTRIBUTING.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b1ad077..752eac1 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,8 +65,9 @@ This document describes how to contribute to ReVanced Library. ## 📖 Resources to help you get started -* [Our backlog](https://github.com/orgs/ReVanced/projects/12) is where we keep track of what we're working on -* [Issues](https://github.com/ReVanced/revanced-cli/issues) are where we keep track of bugs and feature requests + +- [Our backlog](https://github.com/orgs/ReVanced/projects/12) is where we keep track of what we're working on +- [Issues](https://github.com/ReVanced/revanced-cli/issues) are where we keep track of bugs and feature requests ## 🙏 Submitting a feature request @@ -88,11 +89,11 @@ If you encounter a bug while using ReVanced Library, open an issue using the with the maintainers of ReVanced Library. This will help you determine whether your change is acceptable and whether it is worth your time to implement it 2. Development happens on the `dev` branch. Fork the repository and create your branch from `dev` -3. Commit your changes. +3. Commit your changes 4. Submit a pull request to the `dev` branch of the repository and reference issues that your pull request closes in the description of your pull request 5. Our team will review your pull request and provide feedback. Once your pull request is approved, it will be merged into the `dev` branch and will be included in the next release of ReVanced Library -❤️ Thank you for considering contributing to ReVanced Library, +❤️ Thank you for considering contributing to ReVanced Library, ReVanced