|
@@ -90,7 +90,12 @@ There are more guides in [docs/](docs/), e.g. the [Guide for contributing to tra
|
|
|
## How to contribute with a PR
|
|
|
If you would like to contribute by solving an open issue, please fork this repository and then create a branch for the fix.
|
|
|
|
|
|
-Once you push your code to your fork, you'll be able to open a PR into Logseq repository. For more info you can follow this guide from [GitHub docs](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)
|
|
|
+Once you push your code to your fork, you'll be able to open a PR into Logseq repository. For more info you can follow this guide from [GitHub docs](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork).
|
|
|
+
|
|
|
+Enabling "allow edits from maintainers" for PR is highly appreciated!
|
|
|
+
|
|
|
+There's a nice [project board](https://github.com/orgs/logseq/projects/5/views/1?pane=info
|
|
|
+) listing items that easy for contributors to catch-up
|
|
|
|
|
|
And here a list of some [good first issues](https://github.com/logseq/logseq/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22)!
|
|
|
|