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
+21-8
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,14 @@
1
1
# How to Contribute
2
2
3
-
Thank you for your interest in contributing to the dCloud Terraform Provider project! To ensure smooth collaboration and effective development, please review the following guidelines. By following these guidelines, you demonstrate respect for the time and efforts of the project's contributors. In return, they will reciprocate by addressing your issues, evaluating changes, and assisting with your pull requests. We strive to review incoming issues and pull requests within 10 days. Any lingering issues or pull requests inactive for 60 days will be closed.
3
+
Thank you for your interest in contributing to the dCloud Terraform Provider project! To ensure smooth collaboration and
4
+
effective development, please review the following guidelines. By following these guidelines, you demonstrate respect
5
+
for the time and efforts of the project's contributors. In return, they will reciprocate by addressing your issues,
6
+
evaluating changes, and assisting with your pull requests. We strive to review incoming issues and pull requests within
7
+
10 days. Any lingering issues or pull requests inactive for 60 days will be closed.
4
8
5
-
Please note that all interactions within the project are subject to our [Code of Conduct](/CODE_OF_CONDUCT.md). This applies to creating issues or pull requests, commenting on them, as well as any real-time discussions in platforms like Slack, Discord, etc.
9
+
Please note that all interactions within the project are subject to our [Code of Conduct](/CODE_OF_CONDUCT.md). This
10
+
applies to creating issues or pull requests, commenting on them, as well as any real-time discussions in platforms like
11
+
Slack, Discord, etc.
6
12
7
13
## Table Of Contents
8
14
@@ -17,11 +23,15 @@ Please note that all interactions within the project are subject to our [Code of
17
23
18
24
## Reporting Issues
19
25
20
-
Before reporting a new issue, please search our [issues list](https://github.com/cisco-open/terraform-provider-dcloud/issues) to ensure that it hasn't already been reported or fixed.
26
+
Before reporting a new issue, please search
27
+
our [issues list](https://github.com/cisco-open/terraform-provider-dcloud/issues) to ensure that it hasn't already been
28
+
reported or fixed.
21
29
22
-
When creating a new issue, include a clear title, a detailed description, relevant information, and if possible, a test case.
30
+
When creating a new issue, include a clear title, a detailed description, relevant information, and if possible, a test
31
+
case.
23
32
24
-
**If you discover a security vulnerability, please refrain from reporting it through GitHub. Instead, follow the security procedures outlined in [SECURITY.md](/SECURITY.md).**
33
+
**If you discover a security vulnerability, please refrain from reporting it through GitHub. Instead, follow the
34
+
security procedures outlined in [SECURITY.md](/SECURITY.md).**
25
35
26
36
## Development
27
37
@@ -46,14 +56,17 @@ To run the example terraform definitions for the dCloud Terraform Provider, do t
46
56
47
57
1. Navigate to each example directory under `/examples`
48
58
2. Execute `terraform init`
49
-
3. Create an environment variable to hold your Cisco Authentication Token (use a valid token) `export TB_AUTH_TOKEN=abc123`
59
+
3. Create an environment variable to hold your Cisco Authentication Token (use a valid
60
+
token) `export TB_AUTH_TOKEN=abc123`
50
61
4. Execute `terraform apply`
51
62
52
63
## Sending Pull Requests
53
64
54
-
Before submitting a new pull request, please check existing pull requests and issues to ensure that your proposed changes or fixes haven't been discussed in the past or already implemented but not released.
65
+
Before submitting a new pull request, please check existing pull requests and issues to ensure that your proposed
66
+
changes or fixes haven't been discussed in the past or already implemented but not released.
55
67
56
-
When submitting a pull request, include tests for any affected behavior. As we follow semantic versioning, breaking changes may be reserved for the next major version release.
68
+
When submitting a pull request, include tests for any affected behavior. As we follow semantic versioning, breaking
69
+
changes may be reserved for the next major version release.
0 commit comments