3
3
Want to hack on this project? Awesome! Here are instructions to get you started.
4
4
5
5
Additional information can be found in the docs:
6
- [ issue triage] ( https://github.com/docker /linuxkit/blob/master/docs/issue-triage.md ) ,
7
- and [ review process] ( https://github.com/docker /linuxkit/blob/master/docs/reviewing.md ) .
6
+ [ issue triage] ( https://github.com/linuxkit /linuxkit/blob/master/docs/issue-triage.md ) ,
7
+ and [ review process] ( https://github.com/linuxkit /linuxkit/blob/master/docs/reviewing.md ) .
8
8
9
9
## Reporting security issues
10
10
@@ -25,7 +25,7 @@ A great way to contribute to the project is to send a detailed report when you
25
25
encounter an issue. We always appreciate a well-written, thorough bug report,
26
26
and will thank you for it!
27
27
28
- Check that [ our issue database] ( https://github.com/docker /linuxkit/issues )
28
+ Check that [ our issue database] ( https://github.com/linuxkit /linuxkit/issues )
29
29
doesn't already include that problem or suggestion before submitting an issue.
30
30
If you find a match, you can use the "subscribe" button to get notified on
31
31
updates. Do * not* leave random "+1" or "I have this too" comments, as they
@@ -47,7 +47,7 @@ This section gives the experienced contributor some tips and guidelines.
47
47
48
48
Not sure if that typo is worth a pull request? Found a bug and know how to fix
49
49
it? Do it! We will appreciate it. Any significant improvement should be
50
- documented as [ a GitHub issue] ( https://github.com/docker /linuxkit/issues ) before
50
+ documented as [ a GitHub issue] ( https://github.com/linuxkit /linuxkit/issues ) before
51
51
anybody starts working on it.
52
52
53
53
We are always thrilled to receive pull requests. We do our best to process them
0 commit comments