-
Notifications
You must be signed in to change notification settings - Fork 12
Home
Welcome to the github-wiki-action wiki!
testing if I can store coverage reports, but GitHub doesn't show line numbers for rst!!!!
test with diff on GitHub markdown
+ Green
- Red
! Orange
@@ Pink @@
# Gray
the problem with this is no line numbers. Sure we could do
- asdf
- Red +
- 123
-
- this isn't a part of #2. It's from 3
but no line number if no random text in between
HOWEVER, a point to note is that people generally aren't copying code I guess. So maybe having those line numbers inside isn't bad...
1. + reg
+ 1. 123
- 2. 123
# 3. Gray
In that case, the GitHub wiki coverage service would basically work like this:
you'd have a GitHub action running this service. Every time there's a pull request, we'd save our custom MD coverage report generator inside a git path to wiki/coverage-or-user-input/pr-num/all_the_files
and pr-num would be main for the default branch, regardless if it's main or master. Unfortunately, for most teams, this action isn't really worth it. I think in private repos, teams need to pay GitHub team for wiki. So no point for this I guess. And for open source, codecov was a bit of a pain, but obviously much nicer plus it includes a good bit of service like their bot and ci.
other workstation in rst
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1kjhgjhgkjhgkhjgkjhgkghjhkh. k
#. Step 2.
#. Step 3.
weird shading in between
#. Step 1. #. Step 2. #. Step 3. #. Step 1kjhgjhgkjhgkhjgkjhgkghjhkh. k #. Step 2. #. Step 3.
the above looks better than the first. Plus when copying and pasting, it doesn't grab the line numbers. If only GitHub supported rst line numbers arggggg.
I would rather do this in rst too (not markdown) so that we can take advantage of rst highlighting the background
.. raw:: html
<style> .red {color:red} </style>
.. role:: red
An example of using :red:background red????
DOES NOT WORK
remnants of rst testing
#. Step 1.
#. Step 2.gkhgkjhgjhgkjgkjhgkjghgkjhgkjhgkjgkjhgkjhgk
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.
#. Step 1.
#. Step 2.
#. Step 3.