zervo/seb-win-refactoring
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Alas, one more change to the readme. Note to self: Edit the readme online next time...

Browse source
This commit is contained in:
dbuechel 2019-04-11 11:03:35 +02:00
parent 54de6bf1f5
commit 060476d95f
1 changed files with 1 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
README.md
View file

@ -4,12 +4,11 @@ Refactored version of Safe Exam Browser for Windows with Chromium as integrated
**PLEASE NOTE:**\ **PLEASE NOTE:**\
This version is work in progress and not yet meant to be used by the public. See https://github.com/SafeExamBrowser/seb-win/releases for the current, official release of SEB. This version is work in progress and not yet meant to be used by the public. See https://github.com/SafeExamBrowser/seb-win/releases for the current, official release of SEB.
## Status ## Status & Current Build
[![Build Status](https://ci.appveyor.com/api/projects/status/f1iknxq4qmtjjkj3?svg=true)](https://ci.appveyor.com/project/dbuechel/seb-win-refactoring) [![Build Status](https://ci.appveyor.com/api/projects/status/f1iknxq4qmtjjkj3?svg=true)](https://ci.appveyor.com/project/dbuechel/seb-win-refactoring)
[![Unit Test Status](https://img.shields.io/appveyor/tests/dbuechel/seb-win-refactoring.svg)](https://ci.appveyor.com/project/dbuechel/seb-win-refactoring/build/tests) [![Unit Test Status](https://img.shields.io/appveyor/tests/dbuechel/seb-win-refactoring.svg)](https://ci.appveyor.com/project/dbuechel/seb-win-refactoring/build/tests)
[![Code Coverage](https://codecov.io/gh/SafeExamBrowser/seb-win-refactoring/branch/master/graph/badge.svg)](https://codecov.io/gh/SafeExamBrowser/seb-win-refactoring) [![Code Coverage](https://codecov.io/gh/SafeExamBrowser/seb-win-refactoring/branch/master/graph/badge.svg)](https://codecov.io/gh/SafeExamBrowser/seb-win-refactoring)
### Current Build
#### Disclaimer #### Disclaimer
Development builds may be unstable and should thus _never_ be used in a production environment! Development builds may be unstable and should thus _never_ be used in a production environment!