Additional steps required
1. In order to work, the related PR in the documentation repository will also need to be merged, as it contains a job that actually creates the issue. The action in this repository simply triggers an alert and passes information to the other repository.
2. I have created a GitHub bot with the sole purpose of enabling the use of authorisation tokens with tightly-scoped permissions owned by the organization rather than an individual. We need this because we're triggering an action in one repository to do trigger another action in a different repository.
Ownership has been transferred to `bookwyrm-social`. A new private key should be generated, and the `APPLICATION_ID` and `APPLICATION_PRIVATE_KEY` need to be added to the main repository's _Action_ `SECRETS`.
Both repositories (or "All repositories") must be granted access, in the Bot configuration screen.
3. In the main repository settings, _Actions - General_ permissions must be set to _Allow all actions and reusable workflows_.
* Compiles css framework from sass
* Adds watch commands
* Copies existing css to sass file
* Moves sass out of static path
* Removes global linter
I wasn't sure how to customize this, and it's not providing a lot of
additional value on top of the domain-specific linters
* Reverts invalid change to dockerfile
* Changes stylelint path
* Remove unused bulma files
* Properly minifies generated css
* Fixes regression in thread display
* rgba function only works with percents for whatever reason
* Hush stylelint
* Removes trailing zeros
* Compile sass in Django
Co-authored-by: Joachim <joachim.robert@protonmail.com>
* Python formatting
* Updates linter
* Updates commands
* Adds css-config file
Co-authored-by: Joachim <joachim.robert@protonmail.com>
* Stylelint fix
* Removes unused compiled bulma files
Co-authored-by: Joachim <joachim.robert@protonmail.com>