I made a logo! Let's add it to the project, and the README.
Added logo16x16.png, logo128x128.png, and logo.svg to the assets/ folder. (The 128x128 image is for the logo in Gitea, the logo.svg is for the README, and the logo.png is for editing.)
Updated the README to link to pkg.go.dev, and contain the logo.
Added make lint-markdown target, and the lint-markdown CI job.
I made a logo! Let's add it to the project, and the README.
- Added `logo16x16.png`, `logo128x128.png`, and `logo.svg` to the `assets/` folder. (The 128x128 image is for the logo in Gitea, the `logo.svg` is for the README, and the `logo.png` is for editing.)
- Updated the README to link to `pkg.go.dev`, and contain the logo.
- Added `make lint-markdown` target, and the `lint-markdown` CI job.
- Using `make lint-markdown` poses a 'Docker-in-Docker' problem, and the `markdownlint-cli2` container does not have any files that it should.
- Use the dedicated `DavidAnson/markdownlint-cli2-action` GitHub action to process the test instead.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I made a logo! Let's add it to the project, and the README.
logo16x16.png,logo128x128.png, andlogo.svgto theassets/folder. (The 128x128 image is for the logo in Gitea, thelogo.svgis for the README, and thelogo.pngis for editing.)pkg.go.dev, and contain the logo.make lint-markdowntarget, and thelint-markdownCI job.pkg.go.devin README.md 20d43e8b15DavidAnson/markdownlint-cli2-action