Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NF: Teaching Pelita — Caveats and best practices #463

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Debilski
Copy link
Member

Closes #461

This is a first draft with spontaneous thoughts. I think we can still add a bit more knowledge and explanations. It does not need to be merged directly.

Q: Should we rather have it on the root of the repository or in the online docs?

@codecov-io
Copy link

codecov-io commented Mar 21, 2018

Codecov Report

Merging #463 into master will increase coverage by 0.1%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##           master     #463     +/-   ##
=========================================
+ Coverage   65.19%   65.29%   +0.1%     
=========================================
  Files          30       30             
  Lines        3968     3968             
=========================================
+ Hits         2587     2591      +4     
+ Misses       1381     1377      -4
Impacted Files Coverage Δ
pelita/simplesetup.py 72.43% <0%> (+0.58%) ⬆️
pelita/game_master.py 96.24% <0%> (+0.93%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6054961...cc335f9. Read the comment docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants