diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2022-06-09 13:25:12 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-06-09 13:25:12 -0400 |
| commit | e5ef9fd5bc9ba959f134411e548e3820444f484c (patch) | |
| tree | eebbaa37c086af932e223cb6f113e2fbcfeaeb35 /vendor/github.com/seccomp/libseccomp-golang/CONTRIBUTING.md | |
| parent | fd1d0d67fbc1b7c26799370dc153009f9dde50bb (diff) | |
| parent | 7e9767502575f257776477ed0c01fe10ef42b465 (diff) | |
| download | podman-e5ef9fd5bc9ba959f134411e548e3820444f484c.tar.gz podman-e5ef9fd5bc9ba959f134411e548e3820444f484c.tar.bz2 podman-e5ef9fd5bc9ba959f134411e548e3820444f484c.zip | |
Merge pull request #14548 from containers/dependabot/go_modules/github.com/opencontainers/runc-1.1.3
Bump github.com/opencontainers/runc from 1.1.2 to 1.1.3
Diffstat (limited to 'vendor/github.com/seccomp/libseccomp-golang/CONTRIBUTING.md')
| -rw-r--r-- | vendor/github.com/seccomp/libseccomp-golang/CONTRIBUTING.md | 26 |
1 files changed, 9 insertions, 17 deletions
diff --git a/vendor/github.com/seccomp/libseccomp-golang/CONTRIBUTING.md b/vendor/github.com/seccomp/libseccomp-golang/CONTRIBUTING.md index d6862cbd5..c2fc80d5a 100644 --- a/vendor/github.com/seccomp/libseccomp-golang/CONTRIBUTING.md +++ b/vendor/github.com/seccomp/libseccomp-golang/CONTRIBUTING.md @@ -1,31 +1,23 @@ -How to Submit Patches to the libseccomp Project +How to Submit Patches to the libseccomp-golang Project =============================================================================== https://github.com/seccomp/libseccomp-golang This document is intended to act as a guide to help you contribute to the -libseccomp project. It is not perfect, and there will always be exceptions -to the rules described here, but by following the instructions below you -should have a much easier time getting your work merged with the upstream +libseccomp-golang project. It is not perfect, and there will always be +exceptions to the rules described here, but by following the instructions below +you should have a much easier time getting your work merged with the upstream project. ## Test Your Code Using Existing Tests -There are two possible tests you can run to verify your code. The first -test is used to check the formatting and coding style of your changes, you -can run the test with the following command: - - # make check-syntax - -... if there are any problems with your changes a diff/patch will be shown -which indicates the problems and how to fix them. - -The second possible test is used to ensure the sanity of your code changes -and to test these changes against the included tests. You can run the test -with the following command: +A number of tests and lint related recipes are provided in the Makefile, if +you want to run the standard regression tests, you can execute the following: # make check -... if there are any faults or errors they will be displayed. +In order to use it, the 'golangci-lint' tool is needed, which can be found at: + +* https://github.com/golangci/golangci-lint ## Add New Tests for New Functionality |