|
@@ -37,7 +37,7 @@ A great way to contribute to the project is to send a detailed report when you
|
|
|
encounter an issue. We always appreciate a well-written, thorough bug report,
|
|
encounter an issue. We always appreciate a well-written, thorough bug report,
|
|
|
and will thank you for it!
|
|
and will thank you for it!
|
|
|
|
|
|
|
|
-Check that [our issue database](https://github.com/docker/compose-cli/issues)
|
|
|
|
|
|
|
+Check that [our issue database](https://github.com/docker/compose/labels/Docker%20Compose%20V2)
|
|
|
doesn't already include that problem or suggestion before submitting an issue.
|
|
doesn't already include that problem or suggestion before submitting an issue.
|
|
|
If you find a match, you can use the "subscribe" button to get notified on
|
|
If you find a match, you can use the "subscribe" button to get notified on
|
|
|
updates. Do *not* leave random "+1" or "I have this too" comments, as they
|
|
updates. Do *not* leave random "+1" or "I have this too" comments, as they
|
|
@@ -67,7 +67,7 @@ This section gives the experienced contributor some tips and guidelines.
|
|
|
Not sure if that typo is worth a pull request? Found a bug and know how to fix
|
|
Not sure if that typo is worth a pull request? Found a bug and know how to fix
|
|
|
it? Do it! We will appreciate it. Any significant change, like adding a backend,
|
|
it? Do it! We will appreciate it. Any significant change, like adding a backend,
|
|
|
should be documented as
|
|
should be documented as
|
|
|
-[a GitHub issue](https://github.com/docker/compose-cli/issues)
|
|
|
|
|
|
|
+[a GitHub issue](https://github.com/docker/compose/issues)
|
|
|
before anybody starts working on it.
|
|
before anybody starts working on it.
|
|
|
|
|
|
|
|
We are always thrilled to receive pull requests. We do our best to process them
|
|
We are always thrilled to receive pull requests. We do our best to process them
|
Nicolas De Loof