From c52f0b5954e7abefd1ef2921ac935fc6b508aca4 Mon Sep 17 00:00:00 2001
From: Pratiksha Sankhe
Date: Sun, 5 Mar 2023 14:32:39 +0530
Subject: [PATCH 1/2] Improved the community page
---
community.html | 9 ++++++---
css/style.css | 11 +++++++++++
2 files changed, 17 insertions(+), 3 deletions(-)
diff --git a/community.html b/community.html
index 6ac78a1..3752ccd 100644
--- a/community.html
+++ b/community.html
@@ -109,9 +109,11 @@
As a general a open source quality of life improvement, we recommend working on topic branches off of your fork, and keeping your master/develop up to date with the upstream repositories. There's a guide to triangle workflows which may be helpful for using git this way.
- Issues and pull requests should be against the most relevant repository (i.e. where the change would take place).
- Great Bug Reports tend to have:
- A quick summary and/or background
+ Issues and pull requests should be against the most relevant repository (i.e. where the change would take place).
+
+ Great Bug Reports tend to have:
+
+ • A quick summary and/or background
• Steps to reproduce; Be specific and Give sample code if you can.
• What you expected would happen.
• What actually happens.
@@ -119,6 +121,7 @@
• State the device, platform and versions you are running on.
• Notes (possibly including why you think this might be happening, or stuff you tried that didn't work).