Skip to content

Latest commit

 

History

History
140 lines (92 loc) · 4.48 KB

CONTRIBUTING.md

File metadata and controls

140 lines (92 loc) · 4.48 KB
Raw

Hello! Thank you for choosing to help contribute to one of the SendGrid open source projects. There are many ways you can contribute and help is always welcome. We simply ask that you follow the following contribution policies.

Improvements to the Codebase

We welcome direct contributions to the rest code base. Thank you!

Development Environment

Install and Run Locally

Supported Versions
  • Go version 1.14, 1.15 or 1.16
Initial setup:
git clone https://github.com/sendgrid/rest.git
cd rest

Environment Variables

First, get your free SendGrid account here.

Next, update your environment with your SENDGRID_API_KEY if you will test with Swift Mailer.

echo "export SENDGRID-API-KEY='YOUR-API-KEY'" > sendgrid.env
echo "sendgrid.env" >> .gitignore
source ./sendgrid.env
go run examples/example.go
Execute:

See the examples folder to get started quickly.

Understanding the Code Base

/examples

Working examples that demonstrate usage.

rest.go

There is a struct to hold both the request and response to the API server.

The main function that does the heavy lifting (and external entry point) is API.

Testing

All PRs require passing tests before the PR will be reviewed.

All test files are in rest-test.go.

For the purposes of contributing to this repo, please update the rest-test.go file with unit tests as you modify the code.

Run the test:

go test -v

Style Guidelines & Naming Conventions

Generally, we follow the style guidelines as suggested by the official language. However, we ask that you conform to the styles that already exist in the library. If you wish to deviate, please explain your reasoning.

Please run your code through:

Creating a Pull Request

  1. Fork the project, clone your fork, and configure the remotes:

    # Clone your fork of the repo into the current directory
git clone https://github.com/sendgrid/rest
# Navigate to the newly cloned directory
cd rest
# Assign the original repo to a remote called "upstream"
git remote add upstream https://github.com/sendgrid/rest

  2. If you cloned a while ago, get the latest changes from upstream:

    git checkout development
git pull upstream development

  3. Create a new topic branch off the development branch to contain your feature, change, or fix:

    git checkout -b <topic-branch-name>

  4. Commit your changes in logical chunks. Please adhere to these git commit message guidelines or your code is unlikely to be merged into the main project. Use Git's interactive rebase feature to tidy up your commits before making them public.

4a. Create tests.

4b. Create or update the example code that demonstrates the functionality of this change to the code.

  1. Locally merge (or rebase) the upstream development branch into your topic branch:

    git pull [--rebase] upstream development

  2. Push your topic branch up to your fork:

    git push origin <topic-branch-name>

  3. Open a Pull Request with a clear title and description against the development branch. All tests must be passing before we will review the PR.

Code Reviews

If you can, please look at open PRs and review them. Give feedback and help us merge these PRs much faster! If you don't know how, Github has some great information on how to review a Pull Request.