Skip to content

Commit

Permalink
Chore: update dev section of README.MD
Browse files Browse the repository at this point in the history
  • Loading branch information
cnrpman committed Jan 11, 2023
1 parent 719a4ad commit 304b33d
Showing 1 changed file with 6 additions and 1 deletion.
7 changes: 6 additions & 1 deletion README.md
Expand Up @@ -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)!

Expand Down

0 comments on commit 304b33d

Please sign in to comment.