Repository analyzer

#### About
Component for analyze github repository use github statistic API and generate codefresh steps according repo info.

#### Content

* Usage
* Run analyzer without cf integration
* Run analyzer using CLI
* Component description
* Handler types that analyzer support
* Adding new handler documentation

Usage

Examples how use repo analyzer

$3

Run test.js with envs
``
PASSWORD=**2
REPO_OWNER=codefresh-io
REPO_NAME=pipeline-manager
GIT_CONTEXT=github
`

$3

`
analyzer
.step(clone)
.step(build)
.step(push)
.step(packageJson)
.header(stages)
.enrich(stagesEnricher)
.transform(codefreshYaml)
.resolve()
`

$3

1) Transformers - ability to transform from some info to whole yaml file ,
use cases :
- Check that repo contain codefresh.yaml (source github context -> output codefresh yaml path)
- Convert from gitlab to codefresh yaml (source github context -> output codefresh yaml with steps)
Important : after transformer execution if we have result we terminate whole chain (not make any sense to continue)

2) Headers - ability to add some yaml parts before steps key
use cases:
- Add codefresh yaml stages
- Add yaml version

3) Steps - ability to add some step to generated pipeline, like git clone, build, notifications, etc

4) Enricher - ability to enrich each step some additional information, like stage for each step


$3

For add new handler you should create .js in related folder (like analyzer.steps)

Each step has as input analyzer.context (you can access from it githup api, credentials, everything that you need)

`
module.exports = (context) => {

const { repo: { repoOwner, repoName, branch } , git } = context.getContext();

return {
step : {
type: 'git-clone',
description: 'Cloning main repository...',
repo: ${repoOwner}/${repoName},
revision: branch,
git
},
key: 'clone',
group: 'clone'
};
};
`

Where

key - it is step name

group` - logical group, like test, linters, etc, will be helpful in future . (For now using it for stages)