Hello Mr. Diamand,
I see. Initially, I also thought of using .pylintrc but I don’t know
which error should be ignored and which should be fixed so I decided
to adhere 100% to the convention and fix each type of errors in
different patches.
Thank you for your help,
Viet
Signed-off-by: Viet H
On 13 March 2018 at 03:36, Viet Hung Tran wrote:
> Hello Mr. Schneider,
>
> Here is my link for the passed CI build I tested on my fork:
> https://travis-ci.org/VietHTran/git/builds/35210
>
> In order to test .travis.yml configuration alone, I used a sample python
> script call "test.py" that
Hello Mr. Schneider,
Here is my link for the passed CI build I tested on my fork:
https://travis-ci.org/VietHTran/git/builds/35210
In order to test .travis.yml configuration alone, I used a sample python
script call "test.py" that is already successfully tested on my computer
instead of usi
Hi Viet,
> On 12 Mar 2018, at 03:20, Viet Hung Tran wrote:
>
> This is my submission as a microproject for the Google Summer of code.
> I apologize for not setting the [GSoC] in my previous email
> at <20180312020855.7950-1-viethtran1...@gmail.com>.
> Please ignore it.
No worries :-)
> Add a n
This is my submission as a microproject for the Google Summer of code.
I apologize for not setting the [GSoC] in my previous email
at <20180312020855.7950-1-viethtran1...@gmail.com>.
Please ignore it.
Add a new job named Pylint to .travis.yml in order to analyze git-p4 Python
code.
Although Travi
Add a new job named Pylint to .travis.yml in order to analyze git-p4 Python
code.
Although Travis CI have yet to implement continuous integration for multiple
languages. Python package can be installed using apt packages. From there,
pylint can be
installed using pip and used to analyze git-p4.py
6 matches
Mail list logo
