From: Denis Ovsienko Date: Tue, 11 May 2021 22:41:31 +0000 (+0100) Subject: Recommend using the upstream CI in CONTRIBUTING. [skip ci] X-Git-Url: https://git.tcpdump.org/tcpdump/commitdiff_plain/f8491f77ac4d22b32cdf9d89540112c2bb037ffb Recommend using the upstream CI in CONTRIBUTING. [skip ci] CI configuration is a running target, and much of it works on Buildbot, in which pull requests are the only practicable option for 3rd parties. --- diff --git a/CONTRIBUTING b/CONTRIBUTING index 1a1a309c..26fb1ecd 100644 --- a/CONTRIBUTING +++ b/CONTRIBUTING @@ -45,14 +45,9 @@ How to add new code and to update existing code https://github.com/the-tcpdump-group/tcpdump (See https://help.github.com/articles/fork-a-repo/) -2) Setup optional continuous integration (CI) builds - You can setup Travis CI, Cirrus CI and AppVeyor builds for your fork to - test your changes on Linux, FreeBSD, macOS and Windows before opening a - pull request. - (See https://docs.travis-ci.com/user/tutorial/ for information - on setting up Travis CI; go to https://ci.appveyor.com/login and log - in with your GitHub account and select "NEW PROJECT" to set up an - AppVeyor build.) +2) The easiest way to test your changes on multiple operating systems and + architectures is to let the upstream CI test your pull request (more on + this below). 3) Setup your git working copy git clone https://github.com//tcpdump.git @@ -106,7 +101,6 @@ How to add new code and to update existing code 9) Once 100% happy, put your work into your forked repository. git push - This will trigger your fork CI tests, if set up in step 2. 10) Initiate and send a pull request (See https://help.github.com/articles/using-pull-requests/)