Get desktop application:
View/edit binary Protocol Buffers messages
the mapped values are dynamic messages which require the second parsing pass.
how many ticks are in each band [burndown_project, burndown_file, burndown_developer]
how frequently we measure the state of each band [burndown_project, burndown_file, burndown_developer]
always exists
this is included if `--burndown-files` was specified
these two are included if `--burndown-people` was specified
rows and cols order correspond to `burndown_developer`
How many lines belong to relevant developers for each file. The order is the same as in `files`.
how long each tick is, as an int64 nanosecond count (Go's time.Duration)
Used in:
`len(row)` matches `number_of_rows`
Used in:
the first `len(column)` elements are stored, the rest `number_of_columns - len(column)` values are zeros
Used in:
Used in:
Used in:
,https://en.wikipedia.org/wiki/Sparse_matrix#Compressed_sparse_row_.28CSR.2C_CRS_or_Yale_format.29
Used in:
name of each `matrix`'s row and column
is always square
order corresponds to `people_couples::index`
order corresponds to `file_couples::index`
Used in:
developer identities, the indexes correspond to TickDevs' keys.
how long each tick is, as an int64 nanosecond count (Go's time.Duration)
Used in:
all three are of the same length
Used in:
Used in:
The sum always equals to the total number of lines in the file.
Used in:
how long each tick is, as an int64 nanosecond count (Go's time.Duration)
Used in:
Used in:
Used in:
, ,Used in:
this format is versioned
git hash of the revision from which Hercules is built
repository's name
UNIX timestamp of the first analysed commit
UNIX timestamp of the last analysed commit
number of processed commits
duration of the analysis in milliseconds
time taken by each pipeline item in seconds
Used in:
Used in:
Used in:
Used in:
values correspond to `file_couples::index`
Used in:
Used in: