valerio

Hi @sarthak0906, sorry for the late reply. I can have a closer look to the sonar API, but it seems that following endpoint should be enough https://sonarcloud.io/web_api/api/measures. The backend could...

HI @sarthak0906, You can install Perceval with the new backend in a virtual env (see details below) or test it from pycharm (you should create a configuration and pass the...

Nice pointer @aaronnickovich! I use just `coverage` and execute it twice: - `coverage/__main__.py run run_tests.py --source=perceval` to generate the `.coverage` file - `coverage/__main__.py report -m` to get a textual output...

Thank you @imnitishng ! Before starting please have a look at the API doc. If I remember correctly there were two different versions of the API, which have some pretty...

Great @imnitishng ! > Do we open a new issue or discussion is fine here? This thread is fine, thanks!

Based on the classified fields declared at https://github.com/chaoss/grimoirelab-perceval/blob/master/perceval/backends/core/github.py#L102, for each document only the classified fields actually removed from it should appear in the `classified_fields_filtered` attribute. Having a look at the...

We can live with it, so feel free to close this issue. The point is that the classified fileds at https://github.com/chaoss/grimoirelab-perceval/blob/master/perceval/backends/core/github.py#L102 include a mix of attributes present in issues and...

The GitHub issue index contains part of this info. In a nutshell, if an issue contains PR data, the enriched item_type is `pull request` otherwise `issue` (see details at: https://github.com/chaoss/grimoirelab-elk/blob/c723df770bf8ff5f5bc5ee31551c77b73d89ac2c/grimoire_elk/enriched/github.py#L714)....

@alpgarcia @sduenas feel free to jump into the conversation

Thank you for opening this issue @vchrombie! Please could you propose: - the metadata information to be updated within a file - a possible implementation/approach to update the file metadata...