Closed szepeviktor closed 1 year ago
I run the above workflow on each commit to keep my bytes safe.
I am not sure about redbot/assets/red_style.css
as it is a generated file but not minimized.
I suspect css indentation should be set to 2
, just like scss. I'll do that.
Two things:
Makefile.venv
is from an external source, so it shouldn't be changed.Otherwise looks great, thanks!
What's the motivation for not archiving development artefacts? Being able to eg download a zip from GitHub and run tests is useful.
I thought people using github are using git
to get source code ...
The purpose is not to put development files into production.
- I use double blank lines above Markdown section headings and between classes in Python
Done 🍏
Thanks.
Re: .gitattributes - hm. I don't see archiving as the way to get to production, but if you do, you're likely to want to use something like make server
to get the environment set up. Also the archive can be useful for doing things like downloading a zip to check a difference in a PR. Do these files do any harm?
downloading a zip to check a difference in a PR.
This activity also resembles someone not familiar with git.
ZIP archives (git archive HEAD
) are usually used by package managers to download a package.
It may not be true for redbot.
A second thought: redbot may not be a library but an application ...
A second thought: redbot may not be a library but an application ...
Exactly...
Deleted!
Thanks!
Glad to meet your bytes.
@mnot This PR goes into "321" branch.
These commits are the result of the Integrity workflow. It cares about every byte. Please see individual commits.
Review without whitespace changes: https://github.com/mnot/redbot/pull/331/files?diff=unified&w=1