Skip to content
This repository has been archived by the owner on Jun 1, 2024. It is now read-only.

Add a coverage report link to Trac #155

Merged
merged 1 commit into from
May 10, 2016
Merged

Add a coverage report link to Trac #155

merged 1 commit into from
May 10, 2016

Conversation

hawkowl
Copy link
Member

@hawkowl hawkowl commented Dec 2, 2015

No description provided.

@hawkowl hawkowl added the Trac label Dec 2, 2015
@hawkowl
Copy link
Member Author

hawkowl commented Dec 2, 2015

cc @adiroiban @glyph

@glyph
Copy link
Contributor

glyph commented Dec 2, 2015

How would I test this with the VM?

@hawkowl
Copy link
Member Author

hawkowl commented Dec 2, 2015

The instructions from #111 (comment) and the next comment would work, probably. (Or is this a hint to write these in a place in the repo? ;) )

@glyph
Copy link
Contributor

glyph commented Dec 2, 2015

Definitely writing them somewhere near something that looked like documentation would be progress. But it was genuine curiosity in this case, not a hint.

@adiroiban
Copy link
Member

Any progress on this?

I think the coverage links will be of great help.

Can we also have a link to the whole branch, not only on the diff?

Can we have the author + lp bugs fields removed?

Thanks!

@adiroiban
Copy link
Member

For the documentation part, maybe we can update the README file inside the trac service folder with info about how to test it and that are the dependencies.

Thanks!

@hawkowl hawkowl merged commit cf1dd24 into master May 10, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants