diff options
| author | clyne <clyne@bitgloo.com> | 2022-11-17 07:41:09 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-11-17 07:41:09 -0500 |
| commit | 6663c25633a27fcc14d0648bd1afea7ea12f497f (patch) | |
| tree | dcc2ec993db3c4b75c3e7e3df35b0494a9ce1f32 /lib/sol2/CONTRIBUTING.md | |
| parent | da0913771538fd9b1ca538615fd9aa0388608466 (diff) | |
| parent | 57013add5b7c524086272be7d395f9ec5109bde2 (diff) | |
Lib cleanup
Diffstat (limited to 'lib/sol2/CONTRIBUTING.md')
| -rw-r--r-- | lib/sol2/CONTRIBUTING.md | 27 |
1 files changed, 0 insertions, 27 deletions
diff --git a/lib/sol2/CONTRIBUTING.md b/lib/sol2/CONTRIBUTING.md deleted file mode 100644 index c6de308..0000000 --- a/lib/sol2/CONTRIBUTING.md +++ /dev/null @@ -1,27 +0,0 @@ -## Contributing to sol
-
-Looking to contribute to sol? Well, first thing I want to mention is thank you!
-Second of all, this is probably where you should look :)
-
-## Reporting Issues
-
-If you found a bug, please make sure to make an issue in the issue tracker.
-
-The guidelines for reporting a bug are relatively simple and are as follows:
-
-1. Produce a simple, short, compilable test case that reproduces your problem.
-2. Make a descriptive title that summarises the bug as a whole.
-3. Explain the bug in as much detail as you can in the body of the issue.
-
-If you have all of those requirements set, then your issue reporting is golden.
-
-## Submitting a pull request
-
-Submitting a pull request is fairly simple, just make sure it focuses on a single aspect and doesn't
-manage to have scope creep and it's probably good to go. It would be incredibly lovely if the style is
-consistent to those found in the repository.
-
-To help with this, a `.clang-format` is included. Please run it on your code before you push anything.
-
-If you don't meet all of these style guidelines, don't fret. I'll probably fix it. But please
-do make an effort to actually meet them. Otherwise I'm more likely to reject the pull request.
|