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
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
# Contributing Guide For rules_docker_compose
1
+
# Contributing Guide For rules_docker_compose_test
2
2
3
-
This page lists the operational governance model of this project, as well as the recommendations and requirements for how to best contribute to rules_docker_compose. We strive to obey these as best as possible. As always, thanks for contributing – we hope these guidelines make it easier and shed some light on our approach and processes.
3
+
This page lists the operational governance model of this project, as well as the recommendations and requirements for how to best contribute to rules_docker_compose_test. We strive to obey these as best as possible. As always, thanks for contributing – we hope these guidelines make it easier and shed some light on our approach and processes.
4
4
5
5
# Governance Model
6
6
@@ -13,15 +13,15 @@ The intent and goal of open sourcing this project is to increase the contributor
13
13
Use GitHub Issues page to submit issues, enhancement requests and discuss ideas.
14
14
15
15
### Bug Reports and Fixes
16
-
- If you find a bug, please search for it in the [Issues](https://github.com/salesforce/rules_docker_compose/issues), and if it isn't already tracked,
17
-
[create a new issue](https://github.com/salesforce/rules_docker_compose/issues/new). Fill out the "Bug Report" section of the issue template. Even if an Issue is closed, feel free to comment and add details, it will still
16
+
- If you find a bug, please search for it in the [Issues](https://github.com/salesforce/rules_docker_compose_test/issues), and if it isn't already tracked,
17
+
[create a new issue](https://github.com/salesforce/rules_docker_compose_test/issues/new). Fill out the "Bug Report" section of the issue template. Even if an Issue is closed, feel free to comment and add details, it will still
18
18
be reviewed.
19
19
- Issues that have already been identified as a bug (note: able to reproduce) will be labelled `bug`.
20
20
- If you'd like to submit a fix for a bug, [send a Pull Request](#creating_a_pull_request) and mention the Issue number.
21
21
- Include tests that isolate the bug and verifies that it was fixed.
22
22
23
23
### New Features
24
-
- If you'd like to add new functionality to this project, describe the problem you want to solve in a [new Issue](https://github.com/salesforce/rules_docker_compose/issues/new).
24
+
- If you'd like to add new functionality to this project, describe the problem you want to solve in a [new Issue](https://github.com/salesforce/rules_docker_compose_test/issues/new).
25
25
- Issues that have been identified as a feature request will be labelled `enhancement`.
26
26
- If you'd like to implement the new feature, please wait for feedback from the project
27
27
maintainers before spending too much time writing the code. In some cases, `enhancement`s may
@@ -32,7 +32,7 @@ Use GitHub Issues page to submit issues, enhancement requests and discuss ideas.
32
32
alternative implementation of something that may have advantages over the way its currently
33
33
done, or you have any other change, we would be happy to hear about it!
34
34
- If its a trivial change, go ahead and [send a Pull Request](#creating_a_pull_request) with the changes you have in mind.
35
-
- If not, [open an Issue](https://github.com/salesforce/rules_docker_compose/issues/new) to discuss the idea first.
35
+
- If not, [open an Issue](https://github.com/salesforce/rules_docker_compose_test/issues/new) to discuss the idea first.
36
36
37
37
If you're new to our project and looking for some way to make your first contribution, look for
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
-
# rules_docker_compose
1
+
# Bazel rules for running docker-compose tests
2
2
3
3
This bazel ruleset provides a macro so you can run docker-compose tests as bazel test rules. See the [examples](./examples) directory for full usage of the `docker_compose_test` rule.
4
4
5
5
## Bringing the rule into your Bazel repository
6
6
7
-
Check the [latest release](https://github.com/salesforce/rules_docker_compose/releases) for instructions.
7
+
Check the [latest release](https://github.com/salesforce/rules_docker_compose_test/releases) for instructions.
0 commit comments