Skip to content

Latest commit

 

History

History
147 lines (102 loc) · 6.35 KB

CONTRIBUTING.md

File metadata and controls

147 lines (102 loc) · 6.35 KB

How to Contribute

We love Pull Requests! Your contributions help make Octokit great.

Getting Started

So you want to contribute to Octokit. Great! Contributions take many forms from submitting issues, writing docs, to making code changes. We welcome it all. Don't forget to sign up for a GitHub account, if you haven't already.

Getting Started

You can clone this repository locally from GitHub using the "Clone in Desktop" button from the main project site, or run this command in the Git Shell:

git clone [email protected]:octokit/Octokit.net.git Octokit

If you want to make contributions to the project, forking the project is the easiest way to do this. You can then clone down your fork instead:

git clone [email protected]:MY-USERNAME-HERE/Octokit.net.git Octokit

After doing that, run the .\build.cmd script at the root of the repository to ensure all the tests pass.

How is the codebase organised?

The two main projects are the Octokit and Octokit.Reactive projects.

The Octokit.Reactive library is a thin wrapper over the Octokit library - for those who want to use Reactive Extensions (Rx) instead of tasks.

The namespaces are organised so that the relevant components are easy to discover:

  • Authentication - everything related to authenticating requests
  • Clients - the logic for interacting with various parts of the GitHub API
  • Exceptions - types which represent exceptional behaviour from the API
  • Helpers - assorted extensions and helpers to keep the code neat and tidy
  • Http - the internal networking components which Octokit requires
  • Models - types which represent request/response objects

Unless you're modifying some core behaviour, the Clients and Models namespaces are likely to be the most interesting areas.

The clients within a project are organized similarly to the endpoints in the GitHub API documentation

Some clients are "sub-clients". For example, when you navigate to the Issues API you'll notice there's an endpoint for issues. But in the right navbar, there are other APIs such as Assignees and Milestones.

We've tried to mirror this structure. So the IObservableMilestoneClient isn't a direct property of IObservableGitHubClient. Instead, it's a property of the IObservableIssuesClient. And thus you can get to it by going to client.Issues.Milestones.

What needs to be done?

We have a easy-fix tag on our issue tracker to indicate tasks which contributors can pick up.

If you've found something you'd like to contribute to, leave a comment in the issue so everyone is aware.

For v1 of the Octokit.net API, we're looking to support everything that v3 of the GitHub API supports. As this is currently a pre-1.0 library, we're always looking for ways to improve the API to make it easy to work with the GitHub API.

Making Changes

When you're ready to make a change, create a branch off the master branch. We use master as the default branch for the repository, and it holds the most recent contributions, so any changes you make in master might cause conflicts down the track.

If you make focused commits (instead of one monolithic commit) and have descriptive commit messages, this will help speed up the review process.

If you're adding new files to the Octokit project, we have a helper script to synchronize these changes with the Mono* projects in the solution.

Just run this command: .\build FixProjects

Octokit.net also has a suite of tests which you can run to ensure existing behaviour is unchanged. If you're adding new features, please add some tests alongside so the maintainers can sleep at night, knowing their safety blanket is nice and green!

Run this command to confirm all the tests pass: .\build

Running integration tests

Octokit has integration tests that access the GitHub API, but they must be configured before they will be executed.

Note: To run the tests, we highly recommend you create a test GitHub account (i.e., don't use your real GitHub account) and a test organization owned by that account. Then set the following environment variables:

OCTOKIT_GITHUBUSERNAME (set this to the test account's username) OCTOKIT_GITHUBPASSWORD (set this to the test account's password) OCTOKIT_GITHUBORGANIZATION (set this to the test account's organization) OCTOKIT_PRIVATEREPOSITORIES (set this to TRUE to indicate account has access to private repositories)

Once these are set, the integration tests will be executed both when running the FullBuild MSBuild target, and when running the Octokit.Tests.Integration assembly through an xUnit.net-friendly test runner.

Submitting Changes

You can publish your branch from GitHub for Windows, or run this command from the Git Shell:

git push origin MY-BRANCH-NAME

Once your changes are ready to be reviewed, publish the branch to GitHub and open a pull request against it.

A few little tips with pull requests:

  • prefix the title with [WIP] to indicate this is a work-in-progress. It's always good to get feedback early, so don't be afraid to open the PR before it's "done".
  • use checklists to indicate the tasks which need to be done, so everyone knows how close you are to done.
  • add comments to the PR about things that are unclear or you would like suggestions on

Don't forget to mention in the pull request description which issue/issues are being addressed.

Some things that will increase the chance that your pull request is accepted.

  • Follow existing code conventions. Most of what we do follows standard .NET conventions except in a few places. We include a ReSharper team settings file.
  • Include unit tests that would otherwise fail without your code, but pass with it.
  • Update the documentation, the surrounding one, examples elsewhere, guides, whatever is affected by your contribution

Additional Resources