* Add some icons in Readme
* Align icons at left
* Add some more icons
* Remove inline image
- Use relative icons path
* Format Third Party Extensions
as a table
* force website build
* added readme-icons foler with icons for the readme.md file, as well as icons for light and dark modes in the readme.md titles
* restored corrupted svgs for readme-icons
* moved the icons to asset/readme, added icons for Drawio, Hexo and Jetpack Compose
* - Use `develop` branch absolutified links for README images
- Strip dark image theme links before publish to Github and npm
- Clean third party extensions table
* Commit to tag (ony inside master branch)
* Fix differences in README
* Reintroduce link in README logo
* Drop uneeded newline from README
* Fix error in README
* Add newlines for SVGs
* Newlines for all SVGs
* Reuse black icons from library
* Commit using Github Actions bot
* Reuse diagrams.net library icon for white version
* Fix comment
* Bump 'strip-gh-theme-links' action to v2
* removed assets/readme icons
* Test with 'fill=white'
* Test with 'style="fill:white"'
* added filter:invert(1) to PHP, TS, Simple Icons and Blender
* added readme-icons test, changed the name of light icons in assets/readme
* reloaded icons in Readme
* fixed typo in iconsPath for readme-icons test
* fixed typo on the darkiconsPath resolution
* restored absolute paths
* minimized the white icons on assets/readme
* restored test scripts
* Apply changes
* Disable color output testing in CI
* Revert latest change
Co-authored-by: Eric Cornelissen <ericornelissen@gmail.com>
Co-authored-by: Álvaro Mondéjar <mondejar1994@gmail.com>
Co-authored-by: Jorge Amado Soria Ramirez <darksoul.uci@gmail.com>
* Add prettier as a dependency
* Add format command and configure prettier
I opted for single quotes to be in line with other simple-icons projects
I ignore the data file because changing its formatting is quite a bit of
trouble for all open PRs.
* Run prettier
* Replace all functions by arrow functions
* Move prettier configuration to config file
Move it to a file so editors (and other software) can pick up on the
configuration. I went with .js because (a) it allows for comments and
(2) it seems most of the config files are in JavaScript already.
* Add prettier --check when running npm run lint (This adds it to the CI as well)
* Add husky and format changes before committing
* Use object destructuring for imports consistently
* Add shebang and fileoverview to jsonlint.js
* Use PAT to avoid version bump commit problems due to branch protections
Following the instructions of stefanzweifel/git-auto-commit-action [1]
for pushing to branches with branch protections, this changes the create
release workflow to fetch the repo with a PAT (that must belong to an
admin for this to work). As a result, when pushing the version bump
commit, the required status checks are not required (provided the rules
are not applied to admins).
---
1. https://github.com/stefanzweifel/git-auto-commit-action#push-to-protected-branches
* Add warning to not add `on: push` to create release workflow
* Enforce that create-release isn'ttriggered by push events
* Remove executable flag from file mode
Affected: dgraph, django, homebrew, pagekit, uikit
* Add lint step to CI to reject executable icons
Co-authored-by: Eric Cornelissen <ericornelissen@gmail.com>
* Set up caching jest cache for tests in CI
Use actions/cache to cache the jest cache between runs. The cache will
be invalided if the package-lock.json file is updated OR after 7
days [1]. The cache directory for jest is now also configured to be in a
directory called ".jestcache" at the root of this project. This
directory will be ignored by git due to its addition to the .gitignore.
--
1. https://docs.github.com/en/actions/guides/caching-dependencies-to-speed-up-workflows#usage-limits-and-eviction-policy
* Trigger jest cache in CI
* Include date in cache key
This way the cache is invalidated very day
* Add name for caching Jest's cache step
* Demonstrate test failure with cache enabled
* Revert ff915d4660
* Cache dependencies
* Update Jest cache configuration
* Refactor and use Jest cache in Publish workfow
- Refactor out the duplicated sanity check in the publish workflow into
a separate, depended upon, job.
- Use the Jest cache in the Publish workflow.
* Update linter job in CI to just run `npm run lint`
... whereas previously it ran each linter separately. This avoids having
to update the workflow file if a new linter is added (or a linter is
removed).
* Use run_number instead of date for jest cache in CI
* Simplify GitHub release publish job
