Ran
|
Files
35
|
Run time
2s
|
Badge
Embed ▾
README BADGES
|
push
travis-ci
<a href="https://github.com/napalm-automation/napalm/commit/<a class=hub.com/napalm-automation/napalm/commit/895e58be443395dc4bd8f500cecf837c5b6a9c6d">895e58be4<a href="https://github.com/napalm-automation/napalm/commit/895e58be443395dc4bd8f500cecf837c5b6a9c6d">">Add GitHub issue template, as we used to have before (#961) When we used to maintain separare NAPALM drivers, we had an issue template looking like this: https://github.com/napalm-automation/napalm-junos/commit/</a><a class="double-link" href="https://github.com/napalm-automation/napalm/commit/<a class="double-link" href="https://github.com/napalm-automation/napalm/commit/110fec4bc9c50da43701b5019ecd859cc3c35f54">110fec4bc</a>">110fec4bc</a><a href="https://github.com/napalm-automation/napalm/commit/895e58be443395dc4bd8f500cecf837c5b6a9c6d">#diff-faa36bc26a21ed93c8de974753b71507. I was looking today through the issues we currently have open, and I found some of them a bit chaotic, and hard to understand the context / environment the user runs. Additionally, some, e.g., #960, is really hard to follow, and I've included a note to invite the user to check the HitGub markdown manual.
4881 of 6099 relevant lines covered (80.03%)
0.8 hits per line
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|