cloudposse/.github - Githubissues

This repository fulfills several unique functions functions for the Cloud Posse GitHub Organization.

It can contain special org-level files that provide functionality for our organization on GitHub. These files include:
- profile/README.md - the profile README for the Cloud Posse GitHub organization
- CONTRIBUTING.md - how to get started contributing to our projects
- SECURITY.md - our security policy and how to report vulnerabilities
- CODE_OF_CONDUCT.md - our code of conduct covering our community and projects
- SUPPORT.md - where to get support for our projects
It can also act as a source for defaults of some repo-level files that might be found in a new GitHub repo's .github folder. In the event that a new repo is initialized without these files, the repo will behave on github.com as if the default copies of these files were present in the repo. These files include:
- .github/CODEOWNERS - governs required approvals for pull requests
- FUNDING.yml - how to support the project financially
- *[`.github/ISSUE_TEMPLATE/`](.github/ISSUE_TEMPLATE/)** - issue templates for the project
- .github/PULL_REQUEST_TEMPLATE.md - pull request template for the project

Examples

To add all repository bootstrapping files to a new repo:

Copy the .github/workflows/auto-format.yml file from this repository to the .github/workflows folder of the destination repository.
Execute the Auto-format GitHub Action in the destination repository.

✨ Contributing

This project is under active development, and we encourage contributions from our community.

Many thanks to our outstanding contributors:

For 🐛 bug reports & feature requests, please use the issue tracker.

In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

Review our Code of Conduct and Contributor Guidelines.
Fork the repo on GitHub
Clone the project to your own machine
Commit changes to your own branch
Push your work back up to your fork
Submit a Pull Request so that we can review your changes

NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!

🌎 Slack Community

Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.

📰 Newsletter

Sign up for our newsletter and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know. Dropped straight into your Inbox every week — and usually a 5-minute read.

📆 Office Hours

Join us every Wednesday via Zoom for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus a live Q&A that you can’t find anywhere else. It's FREE for everyone!

License

Preamble to the Apache License, Version 2.0

Complete license is available in the [`LICENSE`](LICENSE) file. ```text Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ```

Trademarks

All other trademarks referenced herein are the property of their respective owners.