You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -5,14 +5,14 @@ To make the process easier and more valuable for everyone involved we have a few
5
5
6
6
## Submitting Issues and Feature Requests
7
7
8
-
Before you file an [issue](https://github.com/apache/incubator-horaedb/issues/new), please search existing issues in case the same or similar issues have already been filed.
8
+
Before you file an [issue](https://github.com/apache/horaedb/issues/new), please search existing issues in case the same or similar issues have already been filed.
9
9
If you find an existing open ticket covering your issue then please avoid adding "👍" or "me too" comments; GitHub notifications can cause a lot of noise for the project maintainers who triage the back-log.
10
10
However, if you have a new piece of information for an existing ticket, and you think it may help the investigation or resolution, then please do add it as a comment!
11
11
You can signal to the team that you're experiencing an existing issue with one of GitHub's emoji reactions (these are a good way to add "weight" to an issue from a prioritisation perspective).
12
12
13
13
### Submitting an Issue
14
14
15
-
The [New Issue](https://github.com/apache/incubator-horaedb/issues/new) page has templates for both bug reports and feature requests.
15
+
The [New Issue](https://github.com/apache/horaedb/issues/new) page has templates for both bug reports and feature requests.
16
16
Please fill one of them out!
17
17
The issue templates provide details on what information we will find useful to help us fix an issue.
18
18
In short though, the more information you can provide us about your environment and what behaviour you're seeing, the easier we can fix the issue.
@@ -31,14 +31,14 @@ All code must adhere to the `rustfmt` format, and pass all of the `clippy` check
31
31
32
32
To open a PR you will need to have a GitHub account.
33
33
Fork the `horaedb` repo and work on a branch on your fork.
34
-
When you have completed your changes, or you want some incremental feedback make a Pull Request to HoraeDB [here](https://github.com/apache/incubator-horaedb/compare).
34
+
When you have completed your changes, or you want some incremental feedback make a Pull Request to HoraeDB [here](https://github.com/apache/horaedb/compare).
35
35
36
36
If you want to discuss some work in progress then please prefix `[WIP]` to the
37
37
PR title.
38
38
39
39
For PRs that you consider ready for review, verify the following locally before you submit it:
40
40
41
-
* you have a coherent set of logical commits, with messages conforming to the [Conventional Commits](https://horaedb.apache.org/dev/conventional_commit.html) specification;
41
+
* you have a coherent set of logical commits, with messages conforming to the [Conventional Commits](https://horaedb.apache.org/docs/dev/conventional_commit/) specification;
42
42
* all the tests and/or benchmarks pass, including documentation tests;
43
43
* the code is correctly formatted and all `clippy` checks pass; and
44
44
* you haven't left any "code cruft" (commented out code blocks etc).
- Send [request](mailto:dev@horaedb.apache.org?subject=(Request%to%20join%20HoraeDB%20slack)) to `dev@horaedb.apache.org` to join HoraeDB slack channel
101
-
- Or you can join our [dingtalk group](https://github.com/apache/incubator-horaedb-docs/blob/main/static/dingtalk.jpg)
100
+
- Or you can join our community [here](http://horaedb.apache.org/community/)
102
101
103
102
Read our [Contributing Guide](CONTRIBUTING.md) and make your first contribution!
0 commit comments