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
| <aname="output_s3_bucket_id"></a> [s3\_bucket\_id](#output\_s3\_bucket\_id)| The name of the bucket. |
161
159
| <aname="output_s3_bucket_region"></a> [s3\_bucket\_region](#output\_s3\_bucket\_region)| The AWS region this bucket resides in. |
162
160
| <aname="output_s3_bucket_versioning"></a> [s3\_bucket\_versioning](#output\_s3\_bucket\_versioning)| The bucket versioning status. |
161
+
162
+
163
+
Bug Reports & Feature Requests
164
+
Please use the issue tracker to report any bugs or file feature requests.
165
+
166
+
Developing
167
+
If you are interested in being a contributor and want to get involved in developing this project or help out with our other projects, we would love to hear from you! Shoot us an email.
168
+
169
+
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
170
+
171
+
Fork the repo on GitHub
172
+
Clone the project to your own machine
173
+
Commit changes to your own branch
174
+
Push your work back up to your fork
175
+
Submit a Pull Request so that we can review your changes
176
+
NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!
177
+
178
+
## To Do
179
+
180
+
## Contributing
181
+
182
+
[ToDo are captured within the GitHub project associated with this module](https://github.com/DevOpsNavy/s3-cloudfront-static-website/projects/1)
183
+
184
+
### Bug Reports & Feature Requests
185
+
186
+
Please use the [issue tracker](https://github.com/DevOpsNavy/s3-cloudfront-static-website/issues) to report any bugs or file feature requests.
187
+
188
+
### Developing
189
+
190
+
If you are interested in being a contributor and want to get involved in developing this project or [help out](https://cpco.io/help-out) with our other projects, we would love to hear from you! Shoot us an [email][email].
191
+
192
+
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
193
+
194
+
1.**Fork** the repo on GitHub
195
+
2.**Clone** the project to your own machine
196
+
3.**Commit** changes to your own branch
197
+
4.**Push** your work back up to your fork
198
+
5. Submit a **Pull Request** so that we can review your changes
199
+
200
+
**NOTE:** Be sure to merge the latest changes from "upstream" before making a pull request!
201
+
202
+
## Contributors
203
+
204
+
| Name | Role |
205
+
|------|---------|
206
+
|[Faizan Raza](https://www.linkedin.com/in/faizan-raza-997808206/)| Lead Developer |
0 commit comments