LogoLogo
GoDocGitHub
  • Introduction
  • FAQ
  • Authentication strategies
    • Overview
    • Strategies
      • Azure Certificate Auth
      • Azure Creds Auth
      • Azure Env-based Auth
      • Azure Device Flow
      • SAML Auth
      • AddIn Only
        • Configuration
      • NTLM Auth
      • NTLM (alternative)
      • On-Demand Auth
      • ADFS Auth
      • FBA Auth
      • TMG Auth
      • Anonymous
    • Dynamic auth
    • Custom Auth
  • SharePoint client
    • HTTP Client
    • Fluent API
    • Hooks
    • Retries
    • Context
  • Samples
    • Library Initiation
    • Basic CRUD
    • Documents
    • Chunk upload
    • Permissions
    • Groups & Users
    • Search API
    • User Profiles
    • Change API
    • Attachments
    • Record Management
    • Sending Emails
    • Property Bags
    • Recycle Bin
    • Feature management
    • Advanced item requests
    • Advanced add/update
    • Unmarshaling responses
  • Sandbox
    • Overview
  • Utilities
    • Headers presets
    • Cpass
    • Compatibility matrix
  • Contributing
    • Overview
    • Testing
Powered by GitBook
On this page
  • Intro
  • Code contributing guidance

Was this helpful?

Edit on GitHub
Export as PDF
  1. Contributing

Overview

💪 Contributing to Gosip client

PreviousCompatibility matrixNextTesting

Last updated 5 years ago

Was this helpful?

Intro

First of all, thank you for considering contributing to the project! We really appreciate any activity around it. There are no small contributions and any investment can't be underestimated. You can contribute with feedback, finding and posting an issue, docs suggestion, code commit, or a star ⭐️. All of these encourage us supporting this and other our Open Source projects on a high level.

Gosip is Open Source project hosted on GitHub. We, at , and community, use the library on our production projects for our customers which makes it easier to guarantee stability and maintenance.

The main project repo is located at .

Contributing to the project follows a majority of GitHub and Open Source communities' principles.

Code contributing guidance

  • Target your pull requests to the dev branch.

  • Add/update any docs articles related to your changes embeded to the code or as a separate notes to the PR, which we'd love to publish on docs site.

  • Include a test for any new functionality and ensure all existing tests are passing by running go test command(s), see

    • If you are fixing a bug, include a test that would have caught the bug you are fixing.

  • Keep your PRs as simple as possible and describe the changes to help the reviewer understand your work.

  • If you have an idea for a larger change to the library please and let's discuss before you invest many hours - these are very welcome but want to ensure it is something we can merge before you spend the time.

ARVO Systems
https://github.com/koltyakov/gosip
more here
open an issue