### README Support & Community Section (Markdown)

Source: https://github.com/crowdstrike/community/blob/main/docs/open-source-policy.md

This snippet provides example text for a project's README file. It clearly states that the project is open source and not a formal product, outlines the lack of formal support, and directs users to GitHub Issues for bug reporting and GitHub Discussions for community interaction across various categories (General, Ideas, Q&A, Show and Tell).

```Markdown
# Support & Community Forums
<p>FalconPy is an open source project, not a formal CrowdStrike product, to assist developers implement CrowdStrike's APIs within their applications. As such it carries no formal support, express or implied.</p>

<p>:fire: Is something going wrong? :fire:<br/>
GitHub Issues are used to report bugs. Submit a ticket here:<br/>
[https://github.com/CrowdStrike/falconpy/issues/new/choose](https://github.com/CrowdStrike/falconpy/issues/new/choose)</p>

<p>GitHub Discussions provide the community with means to communicate. There are four discussion categories:<br/>
  * :speech_balloon: [**General**](https://github.com/CrowdStrike/falconpy/discussions?discussions_q=category%3AGeneral) : Catch all for general discussions. <br/>
  * :bulb: [**Ideas**](https://github.com/CrowdStrike/falconpy/discussions?discussions_q=category%3AIdeas): Have a suggestion for a feature request? Is there something the community or project could improve upon? Let us know here.<br/>
  * :pray: [**Q&A**](https://github.com/CrowdStrike/falconpy/discussions?discussions_q=category%3AQ%26A): Have a question about how to accomplish something? A usability question? Submit them here!<br/>
  * :raised_hands: [**Show and Tell**](https://github.com/CrowdStrike/falconpy/discussions?discussions_q=category%3A%22Show+and+tell%22): Share with the community what you're up to! Perhaps this is letting everyone know about your upcoming conference talk, share a project that has embedded FalconPy, or your recent blog.</p>
```

--------------------------------

### Creating a New Local Branch (Shell)

Source: https://github.com/crowdstrike/community/blob/main/docs/contributing.md

Run this command to create a new local branch and immediately switch to it. Replace 'BRANCH-NAME-HERE' with a descriptive name for your branch.

```shell
git checkout -b BRANCH-NAME-HERE
```

--------------------------------

### Cloning a Forked Repository (Shell)

Source: https://github.com/crowdstrike/community/blob/main/docs/contributing.md

Use this command to clone your forked repository from GitHub to your local machine. Replace 'github-username' and 'repository-name' with your specific details.

```shell
git clone https://github.com/github-username/repository-name.git
```

--------------------------------

### Staging Changes (Shell)

Source: https://github.com/crowdstrike/community/blob/main/docs/contributing.md

Use this command to add the contents of changed files to the staging area (index) before committing. Replace 'insert-paths-of-changed-files-here' with the paths to the files you modified.

```shell
git add insert-paths-of-changed-files-here
```

--------------------------------

### Committing Changes (Shell)

Source: https://github.com/crowdstrike/community/blob/main/docs/contributing.md

Execute this command to save the staged changes as a new commit with a descriptive message. The '-m' flag allows providing the message directly on the command line.

```shell
git commit -m "Added Dockerfile for Ubuntu-based deployments"
```

--------------------------------

### Pushing Local Changes to Remote Fork (Shell)

Source: https://github.com/crowdstrike/community/blob/main/docs/contributing.md

Use this command to upload your local commits from the current branch to your remote fork on GitHub. Replace 'BRANCH-NAME-HERE' with the name of the branch you created.

```shell
git push origin BRANCH-NAME-HERE
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.