forgejo/vendor/github.com/smartystreets/assertions/CONTRIBUTING.md

Contributing

In general, the code posted to the SmartyStreets github organization is created to solve specific problems at SmartyStreets that are ancillary to our core products in the address verification industry and may or may not be useful to other organizations or developers. Our reason for posting said code isn't necessarily to solicit feedback or contributions from the community but more as a showcase of some of the approaches to solving problems we have adopted.

Having stated that, we do consider issues raised by other githubbers as well as contributions submitted via pull requests. When submitting such a pull request, please follow these guidelines:

• Look before you leap: If the changes you plan to make are significant, it's in everyone's best interest for you to discuss them with a SmartyStreets team member prior to opening a pull request.
• License and ownership: If modifying the LICENSE.md file, limit your changes to fixing typographical mistakes. Do NOT modify the actual terms in the license or the copyright by SmartyStreets, LLC. Code submitted to SmartyStreets projects becomes property of SmartyStreets and must be compatible with the associated license.
• Testing: If the code you are submitting resides in packages/modules covered by automated tests, be sure to add passing tests that cover your changes and assert expected behavior and state. Submit the additional test cases as part of your change set.
• Style: Match your approach to naming and formatting with the surrounding code. Basically, the code you submit shouldn't stand out.
  • "Naming" refers to such constructs as variables, methods, functions, classes, structs, interfaces, packages, modules, directories, files, etc...
  • "Formatting" refers to such constructs as whitespace, horizontal line length, vertical function length, vertical file length, indentation, curly braces, etc...