Skip to content

Latest commit

 

History

History
88 lines (55 loc) · 3.9 KB

CONTRIBUTING.md

File metadata and controls

88 lines (55 loc) · 3.9 KB
Raw

Azure SDK Contribution Guide

The Azure SDK project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

Azure SDK Blog Contributions

The Azure SDK Blog welcomes contributions related to the new Azure SDKs. Please reach out to us here azsdkblog@microsoft.com if you are interested in contributing a blog post.

Azure SDK GitHub Pages Site Contributions

Here's the general contribution process:

  1. Fork this repo.
  2. Create a new branch.
  3. Commit your changes to that branch.
  4. Do a PR from your fork/branch to azure-sdk/main.

Codespaces

(Recommended) Codespaces is new technology that allows you to use a container as your development environment. This repo provides a Codespaces container which is supported by both GitHub Codespaces and VS Code Codespaces.

GitHub Codespaces

  1. From the Azure SDK GitHub repo, click on the Code button then Open with Codespaces.

  2. Open a terminal pane.

  3. Press Ctrl+Shift+T or execute the following command and Ctrl+Click the link generated. A new window will open with the Azure SDK website.

    bundle exec jekyll serve

When you click the link in Codespaces for the running server, like http://127.0.0.1:4000/azure-sdk/, you will be redirected to the Codespaces url, which will not contain the URL path at the end azure-sdk/ and will display a Not Found error. To fix it, add the azure-sdk/ path at the end.

VS Code Devcontainer

  1. Install the VS Code Remote Extension Pack

  2. When you open the Azure SDK repo in VS Code, it will prompt you to open the project in the Devcontainer. If it does not prompt you, press F1, and select Dev Containers: Open Folder in Container.../

  3. Open a terminal pane.

  4. Press Ctrl+Shift+T or execute the following command and Ctrl+Click the link generated. A new window will open with the Azure SDK website.

    bundle exec jekyll serve

Full Local Setup

Note: We recommend you use codespaces documented above. Getting the right version of Ruby with system dependencies and corresponding gems can be difficult and may not match the Gemfile.lock that was generated in a devcontainer. If you want to work locally, you might consider rbenv to create a virtual Ruby environment which minimizes conflicts with other installations.

This site uses Jekyll and GitHub pages. Installation instructions can be found here: https://jekyllrb.com/docs/installation.

GitHub instructions can be found at https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.

Here's how to setup the site locally:

  1. Install Ruby 3.3.

    You can find complete installation instructions here: https://jekyllrb.com/docs/installation.

  2. Restart your machine.

    You may need to restart your machine after installing Ruby.

  3. Install Jekyll.

    gem install jekyll bundler

  4. Install Dependencies.

    Run the following command from the root of the azure-sdk project.

    bundle install

  5. Open a terminal and execute the following command to start the site:

    bundle exec jekyll serve -I

  6. Open a browser to https://127.0.0.1:4000/azure-sdk to run the site.