Igor Chubin

@chrisallenlane Chris thank you for the feedback. I think that the we should adopt the front-matter approach as well. cheat.sh must support the cheat upstream repository anyway, so why not...

I'm also thinking about limiting the maximum cheat sheet width by 80 characters, and adding this (and maybe some other) check to pull-requests checks

I my opinion, it is better to enforce the width before the merge, so that the files in the repository are already formatted properly, and do not require post-processing. There...

Actually, the checks work very easy: they are just script, that test the repository for compliance. In our case it could be something like: ``` grep -rP '^#.{80}' sheets/ ```...

We will probably use GitHub Actions too. I am using them in some other projects, and I am pretty happy with it. I like your list of checks. I would...

We also should standardize quotes usage in comments: * `backticks` — for verbatim names and code? * 'single quotes' — for ??? * "double quotes" — for ??? After that,...

@dufferzafar Here is our jq cheat sheet. Feel free to extend it, or use for inspiration for your own cheat sheet

A small addition: Timezone must specified in the standard format understandable by pytz, e.g. `Europe/London`, to that this could work: ``` pytz.timezone(tiimezone_description) ``` It should return a short error message...

@martinbra Martin, I am going through old issues: do we have something to do here?

@martinbra I think that your last drawing with fixes was pretty good, and we should use it. And for other cases (e.g. other moon sizes), we should just make the...