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
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,16 @@
1
1
# Contributing to This Repository
2
2
3
-
We welcome your contributions! There are multiple ways to contribute.
3
+
Oracle welcomes your contributions! There are multiple ways that you can contribute.
4
4
5
5
## Opening issues
6
6
7
-
For bugs or enhancement requests, please file a GitHub issue unless the problem is security-related. When filing a bug, remember that the more specific the bug is, the more likely it is to be fixed. If you think you've found a security
8
-
vulnerability, then do not raise a GitHub issue. Instead, follow the instructions in our
9
-
[security policy](./SECURITY.md).
7
+
For bugs or enhancement requests, please file a GitHub issue, unless the problem is security-related.
8
+
9
+
When filing a bug, remember that the more specific the bug is, the more likely it is to be fixed. If you think you've found a security vulnerability, then do not raise a GitHub issue. Instead, follow the instructions in our [security policy](./SECURITY.md).
10
10
11
11
## Contributing code
12
12
13
-
We welcome your code contributions. Before submitting code by using a pull request,
13
+
Oracle welcomes your code contributions. Before submitting code by using a pull request,
14
14
you must sign the [Oracle Contributor Agreement][OCA] (OCA), and your commits must include the following line, using the name and e-mail address you used to sign the OCA:
15
15
16
16
```text
@@ -29,22 +29,22 @@ can be accepted.
29
29
30
30
## Pull request process
31
31
32
-
1. Ensure there is an issue created to track and discuss the fix or enhancement that you intend to submit.
32
+
1. Ensure that there is an issue created to track and discuss the fix or enhancement that you intend to submit.
33
33
1. Fork this repository.
34
34
1. Create a branch in your fork to implement the changes. Oracle recommends using
35
35
the issue number as part of your branch name. For example: `1234-fixes`
36
36
1. Ensure that any documentation is updated with the changes that are required
37
37
by your change.
38
-
1.Ensure that any samples are updated, if the base image has been changed.
38
+
1.If the base image has been changed, then ensure that any examples are updated.
39
39
1. Submit the pull request. *Do not leave the pull request blank*. Explain exactly
40
40
what your changes are meant to do, and provide simple steps to indicate how to validate
41
41
your changes. Ensure that you reference the issue that you created as well.
42
-
1. Before the changes are merged, Oracle will assign the pull request to 2 or 3 people for review.
42
+
1. Before the changes are merged, Oracle will assign the pull request to two or three people for review.
43
43
44
44
## Code of conduct
45
45
46
46
Follow the [Golden Rule](https://en.wikipedia.org/wiki/Golden_Rule). If you'd
47
-
like more specific guidelines, see the [Contributor Covenant Code of Conduct][COC].
47
+
like more specific guidelines, then see the [Contributor Covenant Code of Conduct][COC].
#### Setting Up an OKE Cluster on Oracle Cloud Infrastructure (OCI)
14
15
@@ -26,7 +27,7 @@ If you intent to use `OraOperator` to handle Oracle Autonomous Database lifecycl
26
27
27
28
### Prerequites for Single Instance Databases (SIDB)
28
29
29
-
If you intent to use `OraOperator` to handle Oracle Database Single Instance lifecycles, then read [Single Instance Database Prerequisites](./docs/sidb/SIDB_PREREQUISITES.md)
30
+
If you intent to use `OraOperator` to handle Oracle Database Single Instance lifecycles, then read [Single Instance Database Prerequisites](./docs/sidb/PREREQUISITES.md)
0 commit comments